The SQL Server Data Tools team is pleased to announce an update for SQL Server Data Tools in Visual Studio and the Data-tier Application Framework (DACFX) is now available.
Get it here:
SQL Server Data Tools: https://msdn.microsoft.com/data/hh297027
Data-Tier Application Framework (DACFX): http://www.microsoft.com/en-us/download/details.aspx?id=45886
Support for the latest Azure SQL Database V12 features
Many features were added to Azure SQL Database in V12, and now the developer tools in Visual Studio support V12.
Improved Cross-Platform Schema Comparison
Schema compare has required you to select the “allow incompatible platforms” option when comparing a source to a target that supports fewer objects, as when the source is SQL Server 2014 and the target is SQL Server 2008. Now you can compare anything without selecting the “allow incompatible platforms” option. If any compatibility issues exist, you’ll be notified when you attempt to update the target. Note, though, that incompatible DML, such as procedure bodies, won’t be identified. Look for that feature in a future release.
New advanced publish options
We’ve added new options to increase your control over publishing, including the ability to not drop users. For more details, click here.
Note: A known issue exists in this release with the deployment options configuration for debug deployment. This dialog is accessed through the Project Properties > Debug page by clicking the button labeled Advanced. On that dialog, the new Do Not Drop options are not displayed, but should be. This will be corrected in the next update of SQL Server Data Tools.
Bug fixes to customer-reported issues
This release includes fixes for the following issues:
- Problems encountered on High DPI displays.
- Operations performed on Microsoft Azure SQL Database would fail due to timeout.
- Data compression options on inlined indexes were not honored.
- Grant permission statements were not correctly generated for objects inside of a schema whose authorization is not dbo.
- Import would fail when populating data in a table that has a nonclustered columnstore index.
- Extracting a dacpac from a database would fail if a stored procedure contained an external reference and the verify extraction option was selected.
- Pasting into a View Data cell replaced both the selected and unselected text.
- Updating a value in the View Data grid failed if a column was filtered.
- Schema Compare and publish failed to enforce column order in foreign key constraint definitions.
- Using the output keyword with a table-valued function caused an error.
- Using an inline index with a table-valued function caused an error.
- Updates performed from Schema Compare sometimes failed to re-enabled DDL triggers after disabling them for deployment.