The SQL Server Data Tools team has announced the availability of an update for SSDT Preview. The SSDT Preview update for April 2016 added support for the latest updates of SQL Server 2016 RC3 and various bug fixes.
Give below are the new features available in SSDT as per the official blog:
SQL Server Database
- Always Encrypted Support: For Databases that contain Always Encrypted columns, SSDT and DacFx allows viewing and editing of these databases and publishing from a database project to them. Note that support for altering columns with column encryption present will be coming in a future release.
- Connection dialog and SQL Server Object Explorer: Multiple fixes and improvements.
- The Details page listing advanced connection properties was overhauled to show the full connection string in a multi-line box, and to improve support on High DPI machines.
- We have brought back the traditional error dialog with detailed connection errors. This helps when diagnosing login issues with clearer error messages and a stack trace so that DBAs or CSS can get the information they need to help diagnose your problems.
- For users with minimal permissions we fixed a number of issues around listing databases in the Connection Dialog and SQL Server Object Explorer, viewing the Security folder, and more.
- Azure SQL DB performance when expanding the databases node to list all DBs has been improved.
SSDT installer
- Fixed issue where .Net was being downloaded on uninstall.
- The installer size is now set correctly on High DPI machines.
- Removed the version check blocking SSDT installation if a newer SQL Server version is present.
- Schema Compare: Fixed a performance issue where checking/unchecking multiple items took a long time in Visual Studio.
- Support for using LocalDB 2014 on x86 machines, since there is no x86 version of SQL Server 2016.
Build and Deployment:
- Fixed issue where computed columns were not supported on Temporal Tables.
- The “Execute deployment script in single-user mode” option is ignored when deploying to Azure V12 as this is not supported in cloud scenarios.
For more information on known issues, temporal tables, connection dialog, and set up, check here.
