We’d like to announce the availability of the latest November 2014 release of SQL Server database tooling for Visual Studio. This update is now available for Visual Studio 2012 and 2013. For Visual Studio 2012 use the “SQL –> Check for Updates”
Post by this author
Since we are offering our VS2013 update via the Visual Studio update channel, there aren’t any specific instructions on how to get the download if you need to create an administrative layout. You may need to do this if your firewall or proxy settings do not allow some computers to access the download center.
We’d like to announce the availability of the latest July 2014 release of SSDT. This update is now available for Visual Studio 2012 and 2013. For Visual Studio 2012 use the “SQL –> Check for Updates” tool inside Visual Studio or download via the download link below.
Hello all, there have been some questions around our support for various Visual Studio versions and the update mechanism for them. I hope this will help clarify some of the questions:
Visual Studio 2013 – VS 2013 now has SQL Server tooling built in and shipped as part of the core product.
The SSDT January 2014 release has been updated to support both SQL Server 2012 Parallel Data Warehouse Appliance Update 1 and continues to support SQL Server 2012 Parallel Data Warehouse. This release of SSDT is now PDW version-aware, and the experience is different when connected to SQL Server 2012 Parallel Data Warehouse versus SQL Server 2012 Parallel Data Warehouse Appliance Update 1.
We’d like to announce the availability of SSDT that supports SQL Server 2014 databases. SQL Server Data Tools for SQL Server 2014 CTP2 is pre-release software, does not support upgrade from an existing SSDT install or upgrading to any new versions of SSDT to be released,
The October 2013 release contains an updated installer that does not fail due to certificate validation of the chained MSIs. This release also contains a code change that will allow graceful handling of SQL Server 2014 CTP2 connections where not supported.
We are aware of a new issue today where installing SSDT will fail with the following message “A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.” This is due to an issue in the installer verification code with a SHA256 certificate that expired on 10/6/2013 and we are actively working to update the installer.
The September 2013 release has a targeted fix for the Schema Compare error when working with large display text or high DPI. This release will replace the August 2013 release and contains the same bug fixes with this one additional fix.