Share via

SQL Server Data Tools Preview update for January 2016

The SQL Server Data Tools team is pleased to announce an update for SSDT Preview is now available. The SSDT Preview update for Jan 2016 added support for the latest updates of SQL Server 2016 CTP3.3, more feature enhancements in SSAS and SSIS and various bug fixes.

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

What’s new in SSDT? SQL Server 2016 CTP3.3 database programmability support

SQL Server Analysis Services enhancements

  • Support for calculated columns and row level security for DirectQuery mode.
  • Support for translations of models.
  • Execute TMSL scripts in the SSIS Analysis Services Execute DDL task.
  • many bug fixes
  • For more details on Analysis Service in CTP3.3, see this blog post.

SQL Server Integration Services enhancements

  • Support for ODBC source and destination component.
  • Support for CDC control task.
  • Support for source and splitter component.
  • Support for Microsoft Connector for SAP BW, Integration Services Feature Pack for Azure.

Get it here:

Download SSDT January 2016 Preview for Visual Studio 2015 and Visual Studio 2013

  • The version number for the latest preview in Visual Studio 2015 is 14.0.60203.0
  • The version number for the latest preview in Visual Studio 2013 is 12.0.60202.0

Download Data-Tier Application Framework January 2016 Preview

  • The version number for the latest preview is 13.0.3213.1

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.

Always Encrypted support

  • This feature support is not yet enabled in SSDT.

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.

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
    February 04, 2016
    It's unbelievable that BI Support for VS 2015 is still not yet complete more than 6 months after it RTM'ed. I hope the SSDT team keeps up with the rest of their peers and releases a fully-functional version when the next Visual Studio version is released on the same day. They do it for the Database project. So I can't imagine why they can't do it for the BI pieces as well.
  • Anonymous
    February 04, 2016
    Hi,will the SQL 2012 support be included in the next preview? It is the most awaited functionality for me ...regards and thanks for your fast development.Felix
  • Anonymous
    February 04, 2016
    Your link says "Download SSDT December 2015 Preview for Visual Studio 2015 and Visual Studio 2013"... it does point to the correct version though
  • Anonymous
    February 04, 2016
    Hello @EricThanks for new SSDT update !!!. Bit sad that we still don't have fully suport for SQL 2012/2014 ( *Please note that SSIS designer support for SSIS 2012 and 2014 is not yet included in this update.)Wondering, why SSDT team targeting for SQL 2016 CTP, why can't they focus on provide support for existing SQL Server Release version.Since, we are using VS 2015... so would like to have SSDT support for SQL Server 2012/14.ThanksBinay
  • Anonymous
    February 04, 2016
    Getting an error on install even when using "run as administrator":[150C:1044][2016-02-05T00:03:09]i361: Created a system restore point.[150C:1044][2016-02-05T00:03:09]e000: Error 0x80070003: Failed to create cache directory: C:\ProgramData\Package Cache{8df869a7-9365-4840-8ccd-4bc6f932f58e}[150C:1044][2016-02-05T00:03:09]e000: Error 0x80070003: Failed to create completed cache path for bundle.[150C:1044][2016-02-05T00:03:09]e000: Error 0x80070003: Failed to cache bundle from path: C:\Users\Sean\AppData\Local\Temp{8df869a7-9365-4840-8ccd-4bc6f932f58e}.be\SSMS-Full-Setup.exe[150C:1044][2016-02-05T00:03:09]e000: Error 0x80070003: Failed to begin registration session.[2648:0FA4][2016-02-05T00:03:09]e000: Error 0x80070003: Failed to begin registration session in per-machine process.[2648:0FA4][2016-02-05T00:03:09]e000: Error 0x80070003: Failed to register bundle.[2648:0FA4][2016-02-05T00:03:09]e000: MainViewModel.OnBundleAction: Bundle action failed[2648:0FA4][2016-02-05T00:03:09]i399: Apply complete, result: 0x80070003, restart: None, ba requested restart: No[2648:18B4][2016-02-05T00:03:11]i000: MainViewModel.OpenUrl: Opening url: C:\Users\Sean\AppData\Local\Temp\SsmsSetup\SSMS-Full-Setup_20160205000247.log
    • Anonymous
      June 06, 2016
      Hi Sean,Do you have any update on this?I encountered same issue.PS: I've VS 2013/SSDT which is working fine.-Regards,Ash
  • Anonymous
    February 05, 2016
    I'm still nota clear on something:Will this version allow me to use VS2015, and target different versions of SQL Server with my SSIS projects? If not, is this on the roadmap?Because its 2016, and I'm stuck with VS2012 and VS2013 solutions because of that single SSIS project that target SQL 2012 / 2014.
  • Anonymous
    February 12, 2016
    The comment has been removed
  • Anonymous
    February 19, 2016
    This SSDT preview still errors when you deploy to SQL 2014 in SSISDB, any SSIS packages that contain Script Tasks. This was also mentioned in the previous SSDT preview (see comments). When can we expect a fix for this please?
  • Anonymous
    February 23, 2016
    Hi,Referring to the updates every month we still do not have backward support for 2012/2014 - Are you guys committed to this or is RTM going to ship without this feature and we are stuck installing 3 separate VS again!ThanksToby
  • Anonymous
    February 25, 2016
    The comment has been removed
  • Anonymous
    February 25, 2016
    Hello, I don't see a blog post about the SSDT 2015 preview release (Feb 03, 2016). Would you answer the following if you could:-- What versions of SSIS does this preview support (2016, 2014, 2012, 2008)?-- If prior version support is not included, do you know roughly when this will be available to test?-- Are you planning support for SSIS development via SSDT 2015 all the way back until SSIS 2005? It would be GREAT to have 1 version of VS/SSDT that supports prior versions. I can't wait to test this out.Thank You,Ken Stockwell
  • Anonymous
    March 01, 2016
    I am fully agree with the previous comment.Even RTM build for VS 2013 are so buggy so our team cannot use it.
  • Anonymous
    March 04, 2016
    March 4th and still no February preview...
  • Anonymous
    March 05, 2016
    We've found that our SSDT schema compare timeouts are resolved by following the advice here:https://blogs.msdn.microsoft.com/sqlblog/2014/11/13/timeout-expired-while-publishing-to-sql-database-via-ssdt/We've had this issue from VS2012 through to VS2015 and was getting worse as our SQL database projects were becoming larger, but changing these settings has solved the problem.What was particularly frustrating is in schema compare you don't actually get an error when the timeout occurs it just stops and some of our dev team were misled into thinking no schema changes were found when in fact there were.I would recommend you trying them (and MS to make the increases the default in the next version of SSDT or at least gives proper feedback to users that a timeout has occurred with a link to the above blog)
  • Anonymous
    March 06, 2016
    Can we please have an option to ignore 71501 errors added.Find this a real pain to sort out when its a complex view. Error SQL71501: View: [dbo].[some view] contains an unresolved reference to an object. Either the object does not exist or the reference is ambiguous because it could refer to any of the following objects: [($external referecne)].[dbo].[Customers].[customerid]::.....
  • Anonymous
    March 06, 2016
    @MgSm88 I am very interested in your case and would like to better understand the issue. Would like to contact me at erickang at microsoft dot com?Best regards,Eric KangSQL Data Tools team
  • Anonymous
    March 06, 2016
    @all,I just found out our blog system was updated and it introduced a new filtering rule for comments. All your comments were in pending queue without being noticed. I approved them all (a bit too late). Sorry about it. It's already the next preview update time so many of your questions will be auto-answered with the new preview update. I will catch up for unanswered ones soon. Best regards,Eric KangSQL Data Tools team
  • Last updated on