↓
 
Sql2Go Consulting

Sql2Go Consulting

MS SQL Server Database Development, Tuning, & Admin — ASP.Net Core 5 Development with DevExtreme

  • Home
  • Sql2Go
    • Services
    • Proximity Database
    • Reference Links
      • T-SQL Tuning
        • Indexing
        • Partitioning
      • T-SQL Coding
        • Indexing
      • SSDT
      • SSRS
      • SSIS
      • Azure
      • Development
      • Maintenance
        • Indexing
      • Architecture
      • .Net Framework/ASP.Net
      • Source Control
      • SQL XML
      • Geospatial
  • Contact Megan
  • About
    • Privacy Policy
Home→Published 2016 → June Log in

Monthly Archives: June 2016

SQL Server 2016 Report Designer always upgrades to 2016 RDL schema

Sql2Go Consulting Posted on June 28, 2016 by meganJuly 30, 2016

Update (7/25/16): You should be fine with older versions of Report Server and SSMS 2016/Visual Studio 2015/SSDT, if you do these three things:

  1. Set the appropriate compatibility level for deployment (TargetServerVersion) in the report project properties.
  2. Build the report project before deploying (this may also catch some kinds of errors).
  3. Deploy from the build output directory (bin/Debug by default) rather than directly from the source code directory.

Disclaimer: I have not yet tested this, but the built RDL looks OK.

stackoverflow: Can I control the version of new SSDT reports in Visual Studio?

Original post:

I only have time for a quick post at the moment, but be aware that if you take advantage of the latest SSMS 2016/Visual Studio 2015 SSDT releases, they do (at last) incorporate the SSDT-BI designer templates. The VS 2015 Report Designer, however, always upgrades the edited RDL file to the 2016 RDL schema. Continue reading →

Posted in Development, SQL Server | Tagged Report Designer, SSMS, SSRS, Visual Studio

Recent Posts

  • BundlerMinifier.Core quits working after Visual Studio 2019 update
  • .Net Core 3.1 Azure App Service startup exception: System.IO.DirectoryNotFoundException
  • Link: WDeployConfigWriter Account Issues
  • Specifying Schema Names in Entity Framework Core Code-First Models
  • SQL Server SP or CU upgrade script failures — Do WHAT to my master database?

Categories

  • ASP.Net Core
  • Code
  • Development
  • Entity Framework Core
  • JavaScript
  • Miscellaneous
  • MS Web Deploy
  • Proximity
  • SQL Server
  • Visual Studio 2019

Archives

  • April 2021
  • May 2019
  • December 2018
  • February 2018
  • October 2017
  • August 2017
  • July 2017
  • May 2017
  • April 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • September 2016
  • June 2016
  • September 2015
  • January 2015
  • December 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • October 2013
  • June 2013
  • May 2013
  • March 2013
  • November 2012
  • October 2012
  • September 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2011
  • January 2010
  • February 2009

Tags

Administration ASP.Net Azure BI C# CLR CMS CSV DBA DB Engine Deployment Development ETL Excel Functional Programming Genealogy geospatial Installation LINQ Locking Maintenance MDS Optimization Performance PowerPivot Relational Model Report Designer ReportViewer Security SMO Source Control SP1 SQL Server SQL Server 2012 SQL Server 2016 SSAS SSDT SSDT-BI SSIS SSMS SSRS T-SQL TFS Visual Studio XML

Sql2GoSM is an IT consulting service
located in Sacramento County, California, USA


© 2014-2021 - Weaver Xtreme Theme Privacy Policy
↑ Cleantalk Pixel