This release note is for Microsoft SQL Server Data Tools (SSDT). For more information on getting started with SSDT, please consult Get started developing with SQL Server Data Tools .
Setup may fail when installing SSDT side-by-side
Installation of a second instance of SSDT may fail because when Visual Studio 2010 Service Pack 1 is reinstalled, the source files may not be found automatically. This is a known issue with SP1, detailed in section 2.3.1 of the SP1 readme: http://go.microsoft.com/fwlink/?LinkId=208963#Maintenance.
To resolve this issue, install VS2010 SP1 for the first language, and then install VS2010 RTM + SP1 for the second language. You can then install SSDT for both languages.
Portuguese (Brazil) SSDT not supported on top of English Visual Studio 2010
Installation of SSDT in Portuguese (Brazil) are not supported on top of English Visual Studio 2010 with a Portuguese (Brazil) Language Pack.
To work around this issue, install Portuguese (Brazil) SSDT on a clean operating system without Visual Studio.
Publishing as a contained user may fail to update database properties
When publishing via contained user, the update of some contained database properties fails on incremental deployment. An error won't be thrown for the properties that fail to be updated, so publish still succeeds.
To work around this issue, either publish as a standard user or generate the deployment script and remove all references to the master database, then execute it.
Single User databases are not supported from SQL Server Object Explorer
Single User databases appear in SQL Server Object Explorer, but the database node cannot consistently be expanded and browsed. When in this state, the database will appear with an error glyph and SSDT functionality for this database will be broken. A possible workaround is to remove the server connection from SQL Server Object Explorer and ensure that any other connections to the database outside of SSDT are closed, and then reconnect to the database.
Cannot install stand-alone SSDT to non-default path
When installing SSDT on a machine without Visual Studio, the installation always installs to the default Visual Studio installation path.
SQL CLR remote debugging not supported in SSDT Integrated Shell
If you install SSDT standalone in the Visual Studio Integrated Shell, remote debugging of SQL CLR is not supported. If you attempt to do this, you will see an error - "Unable to debug .NET code. Could not connect to computer ...".
To work around this, install SSDT on a machine that has a pre-existing Visual Studio 2010 installation (Pro and up). Remote debugging of SQLCLR will then be supported in the SSDT environment.