SQL Server Data Tools July Update

The SQL Server Data Tools team is pleased to announce an update for SQL Server Data Tools (SSDT) is now available. The SSDT update for July 2016 adds bug fixing and enhanced support for SQL Server 2016 features such as Always Encrypted and Temporal Table. This update also introduces a 'safe installation' experience. It aims to guarantee the installation of SSDT update will not break existing applications or SQL Server engine that have shared the same components in the past through the new component isolation approach.

Get it here: Download SSDT GA July 2016 for Visual Studio 2015 and Visual Studio 2013

• The version number for GA in Visual Studio 2015 is 14.0.60629.0 (Direct link: https://msdn.microsoft.com/en-us/mt186501)
• The version number for GA in Visual Studio 2013 is 12.0.60629.0 (Direct link: https://msdn.microsoft.com/en-us/dn864412)

This release will be available through Visual Studio Extensions and Updates soon.

Download Data-Tier Application Framework (June 30 2016)

• The version number is 13.0.3370.2

Database Tools - Always Encrypted enhanced support Always Encrypted is a highly anticipated security feature in Azure SQL Database and SQL Server 2016. Always Encrypted allows clients to encrypt sensitive data inside client applications and never reveal the encryption keys to the Database Engine (SQL Database or SQL Server), significantly enhancing security.

What's in this release

For a guided tour of Always Encrypted in SSDT, see this blog post. This release adds full support for Always Encrypted through our core APIs and command line tool (SqlPackage.exe). You can build and publish database projects with full support for all Always Encrypted features.

Limitations:

• In this release, actions that require Azure Key Vault are not supported inside SSDT, but are supported from our SqlPackage.exe command line tool. Database Publish and Data Viewing/Editing scenarios, involving column master keys stored in Azure Key Vault, will not work in this release.
• Generation of column master keys and column encryption keys is currently not supported. Use SSMS or Powershell to create these keys.

What's coming soon

• Support for Azure Key Vault in SSDT. You will be able to publish databases using column master keys stored in Azure Key Vault through the UI, view encrypted table data, and do all other actions that are supported in this release when using column master keys, stored in Windows Certificate Store.
• Improved support for setup of encryption through SSDT.

Database Tools - Temporal Table enhanced support in SQL Server Data Tools

Temporal tables have also received significantly improved support in SSDT this month. Previously there were a number of incremental publish scenarios that would be blocked for temporal tables. This month, we have simplified the experience by unlinking temporal tables before alterations and re-linking once these have completed. This means that Temporal Tables have parity with other table types (standard, in-memory) in terms of the operations that are supported.

Database Tools - SqlPackage.exe and installation changes

We're making changes to isolate SSDT from SQL Server engine and SSMS updates. Full information is in this blog post.

Database Tools

Analysis Services & Reporting Services

If you have any question or feedback, please ping @sqldatatools on twitter, visit our forum and for bugs please create bug reports on our Microsoft Connect page. We are fully committed to improve the SSDT experience and look forward to hearing from you!

• Anonymous
  June 30, 2016
  Is there a plan to update report designer in vs ?For example , newer version of rdlc and more format (such as html)of local report rendering.
• Anonymous
  June 30, 2016
  Hi Yj,We are working on the plan for a two phase release. First is to release the control for use with existing apps that use RDLC and for new 2016 RDL. We hope to have the first phase out soon, but cannot give any dates as they are not yet set. The second phase is to update the RDLC designer in VS to use the SQL 2016 version of the report control. This will come out later, toward the end of the year would be my estimate.
• Anonymous
  July 01, 2016
  Are you guys aware of a problem regarding the Run64BitRuntime flag in SSIS? It doesn't seem to persist across closing and re-opening the solution which is causing a headache for us. Happy to help providing more information if required.
• Anonymous
  July 01, 2016
  Got it! Just moved to new computer and nice to be able to download SSDT and SSMS separately and without a license!
• Anonymous
  July 02, 2016
  Installed the latest SSDT, Visual Studio 2015 with update 3.Convert an existing table to temporal table, then deploy to Azure SQL database, works fine.Update the newly converted temporal table (e.g. update/add an column definition), deploy, get following error: Value cannot be null. Parameter name: reportedElement.and the deployment process hangs there forever.Is it a known issue? Also it seems that the delete of an existing temporal table doesn't work for SSDT. Deployment error after deleting a temporal table.
  • Anonymous
    July 05, 2016
    Hi Rick, these are not known issues - can you confirm you'd installed the July release, version 14.0.60629.0? If so please create a Connect bug (details below) and if possible put in the exact steps (e.g. how the table looked before the change and what change was made, so we can easily reproduce. I will get this looked into.I'd suggest capturing the event log for what is going wrong and then opening a connect bug for this issue at https://connect.microsoft.com/SQLServer/feedback/CreateFeedback.aspx and use the category "Developer Tools(SSDT, BIDS, etc.)". We're trying to track all bugs through connect so that you can tell when we have fixed the issue and we can request more information. Please include the event log (instructions on this below) plus any other useful information you can provide, such as an example of exact steps to reproduce the problem. Gathering an Event Log for SSDTFor diagnostic purposes we would like you to gather an event log for the issue that you are experiencing in SSDT. In order to gather a log and send it to a member of the team, please follow the steps below. 1. Open a new command prompt as Administrator.2. Run the following commandlogman create trace -n DacFxDebug -p "Microsoft-SQLServerDataTools" 0x800 -o "%LOCALAPPDATA%\DacFxDebug.etl" -etslogman create trace -n SSDTDebug -p "Microsoft-SQLServerDataToolsVS" 0x800 -o "%LOCALAPPDATA%\SSDTDebug.etl" -ets3. Run whatever the target/issue scenario is in SSDT.4. Go back to the command prompt and run the following commandslogman stop DacFxDebug -etslogman stop SSDTDebug -ets5. The resulting ETL files will be located at %LOCALAPPDATA%\SSDTDebug.etl & %LOCALAPPDATA%\DacFxDebug.etl and can be navigated to using Windows Explorer.6. Please attach this file when creating the connect bug NOTE - These logs will only be used by Microsoft product team members in order to better diagnose the problem you are experiencing with SSDT and will not be shared elsewhere. If you want to make sure that there is no private information in your ETL file, the SSDTDebug.etl file can be opened and analyzed using the Windows Event Viewer.To do this, open the Windows Event Viewer application. In the right-hand panel, select Open Saved Log. Navigate to the location where you saved the log, open, and review the contents of the trace.Thanks,Kevin
    • Anonymous
      August 10, 2016
      Hi Kevin,For your information: I am suffering the same issue as Rick at the moment, (except ours is publishing to a local SQL Server 2016). I am using SSDT 14.0.60629.0I am trying to generate a publish script of the database changes, and after "Creating publish preview", it is returning "Value cannot be null. Parameter name: reportedElement" and then it hangs.I have just found out that a colleague's version worked to generate the script when using VS SSDT 14.0.60519.0Was there a solution to Rick's issue?Many thanksChris
      • Anonymous
        August 12, 2016
        Same here.
      • Anonymous
        August 15, 2016
        The same on my side. On the previous version of SSDT it worked well. I use sqlpackage.exe from powershell as workaround
      • Anonymous
        August 18, 2016
        Exact same issue here, I'm using SSDT 14.0.60629.0. This is critical, any fix in sight?
        • Anonymous
          August 24, 2016
          The comment has been removed
        • Anonymous
          August 24, 2016
          Nevermind... I got it to deploy, but later the error it kept coming back as I was working...14.0.60629.0
      • Anonymous
        August 25, 2016
        I am having the same issue the August 15th release. I'm using VS 2015 with SSDT 14.0.60812.0 and publishing to a local SQL Express 2016. It publishes fine until I start using a table with SYSTEM_VERSIONING= ON. I can publish the table originally to get the new datetime2 columns in place and turn on versioning. And I can add a new column that goes before those fields. But if I add the new column to the end of the table or I try to make any modifications to an existing column, I get the “Value cannot be null. Parameter name: reportedElement” error.If this can't be easily fixed, is there a way to revert back to the June release that people are saying didn't have this issue?
        • Anonymous
          August 25, 2016
          That did it. Commenting out the system versioning code in the table got past that error.I'm on 14.0.60629.0, looks like July update is broken for temporal tables.
    • Anonymous
      August 25, 2016
      I created a connect itemhttps://connect.microsoft.com/SQLServer/feedback/details/3087775/temporal-tables-broken-in-vs-data-tools-july-update-14-0-60629-0-value-cannot-be-null-parameter-name-reportedelement
      • Anonymous
        August 29, 2016
        All - apologies for the delayed response on this. We have coded the fix for this internally and expect it to be resolved in the SSDT 16.4 update.Thanks,Kevin
        • Anonymous
          September 01, 2016
          The comment has been removed
          • Anonymous
            September 20, 2016
            This fix is included in our latest 16.4 release.Thanks,Kevin
        • Anonymous
          September 06, 2016
          The fix for this is sorely needed.
• Anonymous
  July 04, 2016
  For Visual Studio 2013 users, does this version (12.0.60629.0) include BI templates (integration services, reporting, etc.) for SQL Server 2016?I'm using Windows 8.1 x64 and have VS 2013 Update 5 and SQL Server 2016 installed with Integration Services added. I also have this updated version of SSDT installed (12.0.60629.0), but when using the "new project" dialog in VS 2013, I don't see any BI templates.
  • Anonymous
    July 05, 2016
    Hi Dean, the unified SSDT installer with both database + BI templates is only in VS2015. Links to the installers for previous versions are at https://msdn.microsoft.com/en-us/library/mt674919.aspx - you'll want to install the SSDT-BI for Visual Studio 2013 release.Thanks,Kevin
    • Anonymous
      July 05, 2016
      Thanks for the reply. So, VS 2013 users can't use SSIS or reporting services projects for SQL 2016 without moving to VS 2015?? Or, will the SSDT-BI for SQL 2014 also work for SQL 2016 ?
      • Anonymous
        July 08, 2016
        It's correct that only VS 2015 can target SQL 2016 integration service. Just like the previous versions, SSIS packages designed in previous VS versions can still run on SQL server 2016 as an upgrade will be performed at run time. However no SQL 2016 SSIS features will show up in VS2013 designer so if you would like to use SQL 2016 features VS 2015 should be used.
    • Anonymous
      July 05, 2016
      I wished you guys would have done 2 things, which would have saved me time:(1) on this page where you have the download link for VS 2013, you would have said below that: "Note: this only gives you SSDT features (object explorer, schema compare, etc.), but NOT BI features (Integration services, reporting, etc.). For BI, go this page:....(2) on the main download page for GA release July 2016, the wording "Works best with VS 2015" is very misleading. It makes it sound like it will give all the features for VS 2013, but maybe not the best experience. I wish you would have put similar wording there as I mentioned in #1.Without the clarification, you made it unnecessarily confusing to VS 2013 users.
      • Anonymous
        July 05, 2016
        The comment has been removed
• Anonymous
  July 08, 2016
  The comment has been removed
  • Anonymous
    July 08, 2016
    I saw my own mistake after I posted it.The parameter is INSTALLALL=1 and not /INSTALLALL=1
• Anonymous
  July 08, 2016
  Hello,Please, are you going to fix the SSIS designer in the next version? This version currently has issues in the control flow when selecting (double-clicking) and dragging objects and it has the same issue than previous versions, if you drag and try to reorder the tasks or containers most of times the designer ridiculously expands the work area. https://social.msdn.microsoft.com/Forums/sqlserver/en-US/890a3f6a-e035-4cb0-9858-ae3de3cc5c77/ssis-ssdtbi-visual-studio-2015-control-flow-gui-problems-when-selecting-doubleclicking-and?forum=ssdtAlso it would be nice a bit of formatting for the SQL Command text areas, (I can't believe that the product doesn't have this yet).It's a shame that such a good product like this it's released with those silly bugs, it's annoying.Thanks in advance.
  • Anonymous
    September 21, 2016
    Wow, I thought I was the only one with this problem ;) Thank you very much for taking the time to report it, Gaston!
• Anonymous
  July 09, 2016
  Hi SSDT team,after installing the latest SSDT and SSMS versions on my SQL Sever 2014 Developer/VS 2013 Pro machine, some SQL Server 2016 modules were also installed. One of it is the Export/Import utility 2016 (DTSWizard.exe version 13.0.1601.5) living in C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn. This version does not allow saving SSIS packages because it claims itself beeing an "Express"-version. Also no 64bit version had been installed. To whom may I adress these issues?
  • Anonymous
    July 13, 2016
    Hi, Jörg, This is a known issue of SSIS I/E wizard. It's supposed to be fixed in next release of SSMS (in August). Also, SSMS will not install the 64bit version of I/E wizard, which is by design.
• Anonymous
  July 14, 2016
  This bug:https://social.technet.microsoft.com/Forums/en-US/04bd00de-c884-49f1-aeb2-254acf095282/sql-server-2016-rc3-reporting-services-mdx-problem?forum=sqlreportingservices...is also fixed by 60629 release.It is strange that(a) it was allowed in GA release(b) it is not mentioned in the list of fixed bugs above.It is good to see it fixed, but please, MS team, avoidsuch a show-stopper in GA releases.Thanks,Alex.
• Anonymous
  July 21, 2016
  SSDT OneDesigner gives errors on my SSIS 2012 packages which use Attunity Connector (more than 50% of my packages use that connector).SQL Server 2012 : https://www.microsoft.com/en-us/download/details.aspx?id=29283SQL Server 2014 : https://www.microsoft.com/en-us/download/details.aspx?id=44582SQL Server 2016 : https://www.microsoft.com/en-us/download/details.aspx?id=52950We have a SQL Server 2012 and would love to move from VS2012 with SSIS 2012 to VS2015 with OneDesigner.This would be a great way to prepare for a future update to SQL Server 2016.
  • Anonymous
    July 24, 2016
    Hi Philip,Thanks for reporting that. Could you please share with us the error message and related information?It would be better if you can share with us the package.Tiancong
• Anonymous
  July 28, 2016
  Here is what I am using:Microsoft Visual Studio Community 2015Version 14.0.25424.00 Update 3Microsoft .NET FrameworkVersion 4.6.01531SQL Server Data Tools (SSDTSetup.exe) 14.0.60629.0Microsoft SQL Server Data ToolsCan anyone else confirm this for me?When I go in and create a new SSRS report using the "Report Wizard", I don't get the table style screen anymore...Is this by design?Here is what I am talking about:Choose the Table StyleSlateForestCorporateBoldOceanGenericI don't see this screen anymore in SSRS. Any ideas?
• Anonymous
  July 29, 2016
  Are you going to add multi-select to the Data compare to allow people to check / uncheck a bunch of tables at once instead of having to click every one individually? Our naming convention groups similar tables and sometimes I need to compare one group and not another. Now I have to click every one individually (sometimes over a 100 of them).
• Anonymous
  July 31, 2016
  Missing icons everywhere!
  • Anonymous
    August 03, 2016
    I'm also missing the majority of my toolbar icons in SSMS. I can hover over them to see what they do, but this existed before the update.
    • Anonymous
      August 04, 2016
      Oops, sorry, SSMS isn't part of SSDT thus making my comment not applicable for this post. Would delete comment but can't.
• Anonymous
  August 03, 2016
  Nice to see an update already. After I installed the update, all my measures in a SSAS tabular project were moved to the first two rows of each container table. Incredibly frustrating to have to organize them yet again, especially since we can't move multiple measures at once.
• Anonymous
  August 04, 2016
  does this allow me to build rdl Reports for Microsoft CRM Dynamics Online 2016?
• Anonymous
  December 02, 2016
  Don't know if that has been brought up, but with the SSIS templates, the font size of the connection manager window is too big when I am using a Surface Pro 4. Any word on when this scaling will get fixed?
• Anonymous
  February 16, 2017
  This tool is amazing, im trying to use for sql development. There is one thing that is frustrating me a lot with .sql files in Visual Studio. It doesn't go well with the crlt + comma Navigate To feature. Here a screenshot of the problem reported by other user on visual studio itself http://imgur.com/a/C5gRw