Freigeben über

SQL Server Data Tools Preview update for December 2015

  • Artikel

The SQL Server Data Tools team is pleased to announce an update for SSDT Preview is now available. The SSDT Preview update for December 2015 includes bug fixes and enhancements for the new connection experience for Microsoft SQL Server and Azure SQL Database which was introduced in the November 2015 update. This update also includes the programmability support for SQL Server 2016 CTP3.2 features and enhancements in SQL Server Analysis Service.

What's new in SSDT?

Connection dialog bug fixes

  • Bug fixes for the recent history listing.
  • Resizing of the connection dialog.
  • Adjustment of the default connection dialog size for long database and server names.
  • Change of test connection timeout value to 15 seconds.
  • Proper use of authentication context set in the connection property when loading a database list. 
  • Allowing creation of Azure SQL server firewall rule if the client IP is not registered when loading a database list.

SQL Server 2016 CTP3.2 feature programmability support

  • System-versioned temporal tables are now supported in database projects

SQL Server Analysis Services enhancements

  • Creation of calculated tables.
  • Setting the default for bi-directional cross filters.
  • Please visit the SSAS team blog to learn more.

SQL Server Integration Services enhancements

  • SSIS Hadoop connector supports Avro file format and Kerberos authentication.

Please note that SSIS designer support for SSIS 2012 and 2014 is not yet included in this update.

Get it here:

Download SSDT December 2015 Preview for Visual Studio 2015 and Visual Studio 2013

  • The version number for the latest preview in Visual Studio 2015 is 14.0.51215.0
  • The version number for the latest preview in Visual Studio 2013 is 12.0.51214.0

Download Data-Tier Application Framework December 2015 Preview

  • The version number for the latest preview is 13.0.900.80

Known issues:

Connection dialog

  • Properties change through Advanced Properties dialog may not be retained when the connection is opened next time through History tab.
  • If installing SSDT standalone - without any previous Visual Studio 2015 installation (Community, Pro+, or Express) - Azure login and browse functionality will not be available. To fix, install a version of Visual Studio and update the Azure Tools to version 2.7 or higher.

Temporal Tables

  • Incremental deployment of a in-memory optimized table may fail if table migration occurs. The mitigation is to manually drop System versioning, i.e. the temporal link between two tables prior to table migration to avoid deployment failure.
  • When you create a new temporal table using Project Item template and add columns to it, deployment may fail. The mitigation is not to add any column until the table is deployed first. Once the table is created, you can add columns to the table and deploy it incrementally.
  • When you delete a column from a temporal table using Table designer, adding a subsequent column may not work properly. To avoid it, keep the comma(,) after the last column in the table definition after deleting a column.

SQL Server Object Explorer

  • For users using Active Directory Integrated or Active Directory Password connections who are not server administrators, browsing in SSOX is not working.

Setup

  • If a version of SQL Server 2016 CTP is already installed on the machine, setup may be blocked. This is to avoid breaking components shared by the engine.
  • If installing SSMS Preview, SSDT Preview for Visual Studio 2015, or SSDT Preview for Visual Studio 2013 side by side on the same machine, there may be issues unless all are updated to the latest release.
  • (VS2015) .Net 4.6.1 may not install if there is no version of Visual Studio or the VS Integrated Shell previously installed on the machine. .Net 4.6 will be installed instead.
    • This will result in no Network connections being shown in the new connection dialog.
    • Recommendation is to install .Net 4.6.1 as it contains a number of stability improvements and SQL related fixes.
  • (VS2015) The April 2014 update to Windows 8.1 and Windows Server 2012 R2 Known as KB2919355 is required to install the Visual Studio 2015 Isolated Shell. Please install KB 2919355 before you install SSDT on these operating systems.
  • (VS2015) The SSDT Japanese language installer may fail on the first attempt due to an issue installing the Visual Studio 2015 Japanese language pack. Retrying installation should succeed in installing correctly.

Contact us:

If you have any question or feedback, please visit our forum or Microsoft Connect page. We are fully committed to improve the SSDT experience and look forward to hearing from you!

Comments

  • Anonymous
    December 17, 2015
    Can you please solve the bug, which causes that the "order by name" function for packages in Integration Services cannot be saved? The Packages are still ordered by creation date next time I open the solution. This is a big disadvantage managing bigger BI projects. Also this bug is mentioned on several places. Thank you in the name of all SSDT users.

  • Anonymous
    December 19, 2015
    +1 on the sorting by name bug. It's actually laughable (and embarrassing) how long that bug has been present for in Visual Studio. The BI tools in Visual Studio are such second class citizens it's unbelievable at times.

  • Anonymous
    December 30, 2015
    Loving being on VS 2015 so far, because the git integration is so much better, but I've hit a snag, and not seeing it in the "Known Issues". SSIS project in VS 2015 on the SSDT Dec. 2015 Preview; everything works running from VS.  Deploy to SQL 2014 in SSISDB, and absolutely everything works, EXCEPT, all my my script tasks fail, saying they are corrupted. I know the VSTA version jumped to 14.0, but they're coded in C# and .Net 4.0, which is the compatible framework for SSIS in SQL 2014. Has anyone else run into this?

  • Anonymous
    January 05, 2016
    I wouldn't bother with asking for bugs to be fixed with SSIS, they simply do NOT listen: connect.microsoft.com/.../sql-2012-datatools-ssis-sort-by-name-option-does-not-retain-sort-order-information Matthew Meyer said he'd forward the issue on to the SSIS team here: blogs.msdn.com/.../sql-server-data-tools-preview-update-for-october-2015.aspx ...yet the MSDN forum post here is still untouched by anyone from MS: social.msdn.microsoft.com/.../ssis-sort-by-name My team is dropping SSIS in favor of something we can get support for.

  • Anonymous
    January 05, 2016
    The comment has been removed

  • Anonymous
    January 08, 2016
    "Please note that SSIS designer support for SSIS 2012 and 2014 is not yet included in this update." Then it's very confusing the way its presented here: msdn.microsoft.com/.../mt204009.aspx I'm 8+ hours into trying to rebuild a package and straighten out my IDE after clicking a link below "SSDT and SSDT-BI for SQL Server 2014".

  • Anonymous
    January 10, 2016
    @Janine Great news to hear SSIS multi-targeting support is planned for the Feb release! On a side note, will there be MSBuild tasks for building SSIS/SSAS projects in the future?

  • Anonymous
    January 10, 2016
    HI guys: I'm not sure if you monitor the MSDN forums, but I'd just like to alert you to this thread I started today regarding what looks to be a bug in the ignore/exclude functions when creating a publish profile. social.msdn.microsoft.com/.../publish-settings-exclude-partition-schemes-not-working

  • Anonymous
    January 19, 2016
    And want to contact MS Support to investigate but there is no "product" called Sql Data Tools - do I contact the Visual Studio team or the SQL Server team?

  • Anonymous
    January 19, 2016
    Nevermind - I have a solution of 33 projects, a mix of SQL reporting services, 4 interdependent database projects, and several C# and VB.NET projects, both app and test projects.  I was in the process of upgrading them all to VS 2015 from 2012, while switching the DB projects to SQL 2014 from SQL 2012 and the frameworks from .net 4.0 to .net 4.6.1.   I tried to do them all at once, but that gave me several warnings in the database projects regarding references to tables in the sys schema as well as calls to the master sprocs sp_xml_preparedocument.  I ended up undoing all my changes, and then doing only the SQL changes first.  I also deleted all database references, including the System databases, upgraded the project setting to 2014 and then re-added the database references.  That seemed to be good and I got a clean build after that.  I checked those in then changed the frameworks to .NET 4.6.1 and then got a clean build without any warnings (after upgrading a few NuGet packages).  Everything seems fine now.

  • Anonymous
    January 19, 2016
    Installing the latest preview breaks Lightswitch apps in VS2015. I can no longer create new lightswitch apps.

  • Anonymous
    January 19, 2016
    Are CDC controls provided in the toolbox? I can't find them. Are they provided by Microsoft or Attunity?

  • Anonymous
    January 25, 2016
    The incrementing row count on a Data Flow is totally inconsistent. When it is run sometimes it shows, sometimes it doesn't and sometimes it displays the wrong number of records!Seems to be totally random.

  • Anonymous
    February 18, 2016
    I checked the latest preview, still no Ignore Column Order option. Do you have any plan to add it back? If not, please announce it officially so we can move on.