Thursday, August 16, 2012 6:38 AM
I'm using fresh installation of Visual Studio 2012 RTM on Windows 8 RTM. I've created a new database project and when I hit the Deploy Selection command, it won't deploy the database to Local DB.
What do I have to do to deploy database created using SSDT? (I need to only deploy the database, I *don't* want to run the whole solution using the F5)
-- Jozef Izso (MCPD)
Thursday, August 16, 2012 6:06 PM
That is a bug that the Deploy menu commands appear for our project and are a no-op, thanks for reporting this!
In the meantime, there is a workaround to make F5 only build/deploy the database project in a mixed solution:
- Go to Build menu > Configuration Manager
- For the Debug configuration, check Build and Deploy for the database project and uncheck Build for other projects in your solution. Now when you hit F5 it will just build and deploy the database project. When you need Start Debugging (F5) to apply to the whole solution again you'll need to go back to the build configuration manager.
Hope that helps for now, thanks!
Sarah McDevitt Program Manager SQL Server Data Tools
Tuesday, September 11, 2012 4:51 AM
The database "Publish" command in Visual Studio 2012 works as the "Deploy" command in Visual Studio 2010. No workaround is needed.
We've got a lot of TSQL warnings after converting VS2010 database projects into VS2012 (no warnings before the conversion). With "Treat T-SQL warnings as errors" unchecked, both Build and Publish executions could go through. All database pieces were deployed without any issues.