Share via

Special update: SSDT Preview Update with SQL Server 2016 RC2 support

  • Article

Update: Now that SSDT is GA, please go to the main SSDT download page to get SSDT. The post below has been preserved for reference.

Original post:

This month we are not releasing the standard SSDT monthly refresh on our main download page. We'll cover why we're doing this and how to get support for the latest SQL Server 2016 RC2 compatible SSDT download in this post. If you are an SSRS user we recommend you read the whole post, for anyone else you can skip to the bottom for download links.

Who Should download this SSDT Update
SSIS users who target SQL Server 2016, and anyone looking to try new SSAS or SSRS features added in RC1 or RC2 should download this update. For anyone else, we recommend waiting 2-3 weeks until our next update which resolves the known issue described below. Before downloading and installing this update, please read the following issue description first.

Known issue with this update
Report deployment can fail when targeted SQL Server 2014 or earlier

When build or deploy a Reporting Services report project whose TargetServerVersion is set to “SQL Server 2008” or “SQL Server 2008 R2, 2012, or 2014,” you might encounter the following error: “Attribute MustUnderstand was detected in the report. SQL Server 2014 Reporting Services and earlier do not support MustUnderstand. Either reduce the error level to a value less than 2 or change the TargetServerVersion to a version that supports MustUnderstand.”

The issue is that the MustUnderstand attribute, currently only prefixed to the DefaultFontFamily element, is incorrectly perceived as an item that needs to be downgraded instead of removed. This issue will be fixed in the next update of SSDT.

Work around if you want to use SSRS against SQL Server 2014 or lower:
Set the project’s ErrorLevel to 1 or 0 in the project properties to change the error to a warning. Note that a side-effect of lowering the error level is possible automatic deletion of elements incompatible with the TargetServerVersion. For details about error levels and project properties, see Set deployment properties.

Download SSDTSetup.exe for Visual Studio 2015 - https://msdn.microsoft.com/en-us/library/mt204009.aspx

Comments

  • Anonymous
    April 06, 2016
    The comment has been removed
    • Anonymous
      April 06, 2016
      Hi Jeroen,For your case, please ignore this post - i.e. any developer who needs to develop BI on SQL Server 2014 or earlier version using Visual Studio 2015 and who do not need to try out SQL Server 2016 RC1 and RC2.I would recommend installing SSDT preview from the main download page https://msdn.microsoft.com/en-us/mt429383 unless you must develop your project in SQL Server 2016 RC1 and RC2. SSDT version we linked in this blog is only for SSIS developers who's currently experiencing SxS installation issue with SQL Server 2016 RC1 and SSDT installed on the same machine. And SSAS and SSRS developers who's trying out SQL Server 2016 RC1 and RC2.Again, for developing SQL Server 2014 and earlier on Visual Studio 2015, please ignore this post and download the latest official preview update from https://msdn.microsoft.com/en-us/mt429383 which is the main entry for downloading and installing SSDT.
  • Anonymous
    April 06, 2016
    The comment has been removed
  • Anonymous
    April 07, 2016
    Installing this fixed the SSIS SaveAndUpdateVersionToXML error. Horay!
  • Anonymous
    April 08, 2016
    Visual studio 2015 with latest SSDT preview (SQL Server Data Tools 14.0.60316.0), trying to deploy existing multidimensional cubes project to SSAS 2012.Can't deploy from VS2015 :Error -1055981560 : 1200 is not a valid value for this elementError -1055981548Found error in .asdatabase file build - 1200 (Must be 1100 ?).Multidimensional must be CL 1100 - Tabular 1200.https://msdn.microsoft.com/en-ca/library/gg471593.aspx
  • Anonymous
    April 08, 2016
    Sorry, talking about compability mode 1200, must be 1100 for multidimensional databases. 1100
  • Anonymous
    April 12, 2016
    I'm running this build and having troubles saving certain settings when using the designer. I have a foreach loop container that uses the schema rowset enumerator against an access database. It never holds this setting after closing the IDE. I click save and save the package, but it resets to File enumerator (default) after closing / re-opening the solution in visual studio 2015. In addition, if I modify the debug settings to set 64bitruntime to false that is not held after re-opening either. Is there somewhere I can report these sort of items to the dev team?
  • Anonymous
    April 14, 2016
    Should this work with Visual Studio for Windows Desktop, or does it require an Isolated Shell installation?https://social.msdn.microsoft.com/Forums/sqlserver/en-US/40e7993d-0a37-4663-84ed-3bb07136d19c/ssdt-bi-in-visual-studio-2015-express-for-desktop-installation-order?forum=ssdtregards
    • Anonymous
      April 14, 2016
      Hi Felix, I've responded on the forum thread. Let's sync there and see if the answer helps solve you issue.-Kevin
  • Anonymous
    October 05, 2016
    The comment has been removed