Microsoft SQL Server Data Tools for SQL Server 2014 CTP2
Posted on: 10/26/2013 09:42 AM

Microsoft has released Microsoft SQL Server Data Tools for SQL Server 2014 CTP2

Microsoft SQL Server Data Tools for SQL Server 2014 CTP2


SQL Server Data Tools provides an integrated environment for database developers to carry out all their database design work for any SQL Server platform within Visual Studio. SQL Server Data Tools for SQL Server 2014 CTP2 is pre-release software, does not support upgrade, and should be installed only on a clean machine. This toolset should not be used against production SQL Server databases.

SSDT SQL Server 2014 CTP2 supports targeting and developing for SQL Server 2014 CTP2 databases. Provided in the VS2012 shell, this includes the project system, deployment, online experience through SQL Server Object Explorer and T-SQL Editor.

Known limitations:

Modifying a Memory Optimized table will drop and recreate the table during deployment without moving data. This could result in data loss. We suggest moving data to a temporary table before deploying changes through SSDT.
There are instances where running Extended TSQL verification will cause Visual Studio to close when publishing a database project. We recommend turning off the Extended TSQL verification option in the database project properties.
Default constraints on a Memory Optimized table are not recognized by SSDT when working in the SQL Server object browser or initially publishing a project. If you have them in your project and do additional publish, SSDT will try to alter the table to add the default constraint which is not supported on memory optimized tables.
The table designer design pane will not support all new properties. Users can work around this by typing the syntax into the script pane.
The data compression option on clustered column store indexes is not supported.

SQL Server Data Tools for SQL Server 2014 CTP2 is pre-release software, does not support upgrade, and should be installed only on a clean machine. This toolset should not be used against production SQL Server databases. We appreciate all feedback and encourage use of our forum or Microsoft Connect site.



Printed from NT Compatible (http://www.ntcompatible.com/news/story/microsoft_sql_server_data_tools_for_sql_server_2014_ctp2.html)