Share via

Announcing the General Availability (GA) Release of SSDT 17.0 (April 2017)

  • Article

We are pleased to announce that SQL Server Data Tools 17.0 is officially released and supported for production use. This GA release includes support for SQL Server 2017 and SQL Server on Linux including new features such as Graph DB. It includes several features that we have consistently received requests for via MSDN forums and Connect and contains numerous fixes and improvements over the 16.x version of the tools. You no longer need to maintain 16.x and 17.0 side-by-side to build SQL Server relational databases, Azure SQL databases, Integration Services packages, Analysis Services data models, Azure Analysis Services data models, and Reporting Services reports. From all the SSDT teams, thank you for your valuable feedback and suggestions!

Additionally, for relational and Azure SQL databases SSDT 17.0 GA includes a highly requested improvement to ignore column order in upgrade plans as well as numerous other bug fixes. 

In the Business Intelligence area, SSDT 17.0 GA supports Azure Analysis Services in addition to SQL Server Analysis Services. It features a modern Get Data experience in Tabular 1400 models, including DirectQuery support (see the blog article “Introducing DirectQuery Support for Tabular 1400”) and an increasing portfolio of data sources. Other noteworthy features include object-level security to secure model metadata in addition to data, transaction-performance improvements for a more responsive developer experience, improvements to the authoring experience of detail rows expressions, and a DAX Editor to create measures and other DAX expressions more conveniently.

For Integration Services, SSDT 17.0 GA provides an authoring package with OData Source and OData Connection Manager connecting to the OData feeds of Microsoft Dynamics AX Online and Microsoft Dynamics CRM Online. Moreover, the project target server version supports SQL Server 2017 so you can conveniently deploy your packages on the latest version of SQL Server.

So please download SSDT 17.0 GA from /en-us/sql/ssdt/download-sql-server-data-tools-ssdt and update your existing installations today! Send us your feedback and ask us questions on our forum or via Microsoft Connect.  We look forward to hearing from you.

This release also includes an update to the DacFx Nuget packages published on https://nuget.org.

Comments

  • Anonymous
    April 20, 2017
    Does this release support Visual Studio 2017? If not, is the an ETA on that support?
  • Anonymous
    April 20, 2017
    Installing this broke all of my SSRS/SSAS projects - they now show in the solution explorer as (incompatible).Not very helpful :(
    • Anonymous
      April 20, 2017
      Repairing SSDT didn't help - all SSDT projects show as (incompatible). VS 2015 Enterprise - previously using the 14.0.61021.0 build of SSDT, which worked (mostly) fine.
      • Anonymous
        April 21, 2017
        You'll need this https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftReportProjectsforVisualStudio
      • Anonymous
        April 24, 2017
        Uninstalling this new release and reinstalling 14.0.61021.0 made my projects load again. I might just wait for the next release before trying another update.
      • Anonymous
        April 24, 2017
        Well, it almost fixed it. Now VS cannot open SQL files. The following error appears in the ActivityLog.xml file:LegacySitePackage failed for package [Microsoft SQL Server Data Tools]Source: 'Microsoft.VisualStudio.Data.Tools.Package' Description: Could not load file or assembly 'Microsoft.Data.Tools.Schema.Sql, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Data.Tools.Schema.Sql, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. File name: 'Microsoft.Data.Tools.Schema.Sql, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' at Microsoft.VisualStudio.Data.Tools.Package.UI.DataPackage.Initialize() at Microsoft.VisualStudio.Shell.Package.Microsoft.VisualStudio.Shell.Interop.IVsPackage.SetSite(IServiceProvider sp) WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
        • Anonymous
          April 24, 2017
          Finally! Doing a repair on VS2015 itself restored the SQL editor. Better part of a day wasted by trying this SSDT release.
          • Anonymous
            April 24, 2017
            Arrrgh. Except that repairing VS2015 broke SSMS. What a tangled web of nonsense.
          • Anonymous
            April 24, 2017
            ...and repairing SSMS seems to have restored everything to its normal level of unreliability - i.e. works most of the time.
          • Anonymous
            April 26, 2017
            Wow! I am convinced to not try this release after this horror story. And not even a response from the team... Yeah I will wait till it "bakes" a bit more.
  • Anonymous
    April 21, 2017
    After install, VS2015 can`t start !
    • Anonymous
      April 21, 2017
      After opening old project, all ok
  • Anonymous
    April 21, 2017
    The DAX editor window looks horrible is you are using a dark color scheme for Visual Studio. Doesn't seem to be a way to change these colors under the fonts and colors settings either...
    • Anonymous
      April 25, 2017
      The comment has been removed
      • Anonymous
        May 10, 2017
        I've noticed that more developers are using dark themes now. What is the appeal of this? Is it a fashion/hype thing, or are there some benefits to using them (better on the eyes, or something). For me it seems as more of a strain on the eyes with a black background.
        • Anonymous
          January 25, 2018
          The comment has been removed
  • Anonymous
    April 25, 2017
    When will Microsoft.Data.Tools.Msbuild nuget be updated with the latest DacServices (Microsoft.SqlServer.Dac.dll)ThanksAndrew
  • Anonymous
    April 25, 2017
    On the DacFx 17.0 download page, the links for SQLSysCLRTypes.msi dependency files appear to be reversed. The x64 link is pointing to the x86 version and vice versa.
  • Anonymous
    April 26, 2017
    When SSDT 17.0 will be supported on team build server?I've tryied it, all works fine, but I can't use because the build fails on team build server :(
  • Anonymous
    April 26, 2017
    Please clear-up the confusion around this SSDT release and VS 2017. It seems like this release is for VS 2015, and that VS 2017 users need to get updates from VS 2017 itself. Also, please clear-up the confusion around VS 2017 and SSIS and SSRS.
    • Anonymous
      August 11, 2017
      SSIS (in visual studio 2017) might be available next week when 15.3 is released.Source:https://developercommunity.visualstudio.com/content/problem/51221/vs2017-ssdt-no-project-templates-for-ssis.html
  • Anonymous
    May 02, 2017
    For SSIS script task with this release, it generates script version 15.0, and when you try to add the package to SQL 2016 SSIS RTM (without SP1), it says "script version 15.0 is not compatible with this version of Integration Services." The previous version of SSDT generated script version 14.0.
  • Anonymous
    May 08, 2017
    Spend 2 days trying to fix my VS 2015 + SQL 2016(ssms) ... after install VS didn't open and SQL SSMS also start fail. I'll come back after couple months to try again.
  • Anonymous
    May 09, 2017
    The SSIS script tasks that it generates are not compatible with SQL Server 2016 RTM.See the comment by "Jones".
    • Anonymous
      May 17, 2017
      Any update on when/if this is going to be fixed? We really could use real DAX support in our SSRS reports that is in the current release but can't use that as installing this update breaks our SSIS package on our server.
      • Anonymous
        August 14, 2017
        The comment has been removed
  • Anonymous
    May 22, 2017
    The comment has been removed
  • Anonymous
    May 25, 2017
    I've installed the Analysis Services and the reporting services (The Microsoft Analysis Modelling Services Nuget hinted at here: https://blogs.msdn.microsoft.com/analysisservices/2017/03/09/introducing-sql-server-data-tools-for-analysis-and-reporting-services-for-visual-studio-2017/ package isn't to be found).I still cannot open a dtsx file though. Any advise?The link in the update error takes you to https://go.microsoft.com/fwlink/?LinkId=660342&projecttype=D183A3D8-5FD8-494B-B014-37F57B35E655 which redirects you to http://dotnetredir.azurewebsites.net/index.html which is totally useless.Is there another package I need to install to be able to work with SSIS?
  • Anonymous
    July 17, 2017
    The comment has been removed
  • Anonymous
    July 17, 2017
    OMG, the performance improvements are AMAZING! I had started manually editing the BIM file since the last version was so slow. This version is turning a 5 hour job into a 30 minute job. Well done guys!
  • Anonymous
    July 19, 2017
    Has there been any new developments on this? Can we at least get a beta release date?
    • Anonymous
      July 19, 2017
      They actuallly released 17.1 about a month later ( around mid May ) but they didn't post a blog about it.
  • Anonymous
    August 21, 2017
    https://docs.microsoft.com/en-us/sql/ssdt/changelog-for-sql-server-data-tools-ssdt#ssdt-172 they reference this blog for more information about the 17.2 SSDT release. For SSAS & SSRS there are now VS extensions, however SSIS seems to be only available with the SSDT standalone installer, but not ready for VS2017 yet. Sorry! There was a brief moment when I thought Microsoft will get this finally sorted out but we are going just the opposite direction. Rarely seen such a chaos in a product strategy - message. Please get your act together, communicate through one single channel with a consistent (at least a coordinated) message towards your (paying) customers.
  • Anonymous
    September 10, 2017
    When is SSDT going to support developing SQL Data Warehouse projects on Azure? We need this ability now!
    • Anonymous
      November 06, 2017
      Hi Brian, I' encourage you to create a Connect item with this request, or upvote existing ones. At present this isn't on our roadmap, but we re-evaluate requests during planning every 6 months or so. Hearing requests from users of DW for tools support is important and can help get this prioritized.Regards,Kevin
  • Anonymous
    December 04, 2017
    The comment has been removed
  • Anonymous
    December 07, 2017
    Where is SqlPackage.exe? It isn't in any of the locations that previous blog articles and help docs discuss, and it doesn't get added to my PATH. How do I get it, from this version?
  • Anonymous
    December 18, 2017
    Is this blog going to be updated any more? It used to be a good place to keep up with SSDT
  • Anonymous
    December 20, 2017
    SSDT appears to be the tool i am looking for in regards to progressing in some DevOps initiatives in our department, but importing a LARGE and COMPLEX database is very cumbersome in the tool. If performance can be increased for daily development in a large database project, the adoption of this tool would be so much easier.
  • Anonymous
    December 12, 2018
    Hi, Is this blog alive. Since we are now unable to read anything new related to SSDT, Specially Graph integration in SSDT. Is there a new blog for SSDT and this is expired?
  • Anonymous
    January 07, 2019
    Where are you blogging now? It has been a very long time since a post was made here.