I'll echo jvolters sentiment on a separate part of the VS integration. Our team uses Rapid App. Dev. and we push out individual changes constantly, so in order to deploy changes to our source-controlled stored procedures, we often make the change right in Visual Studio, run against test, then run against staging, and if all went well, we then run against production, all within Visual Studio 2008. Since 08 can't connect to our new SQL '12 I tried both SSDT 2010 and SSDT 2012, and in both cases, there is no option to be prompted for a connection. You have to set the connection in Tools->Options, and then if you want to connect to a different database, you have to go back to Tools->Options and change the "default" connection. This is very cumbersome and as soon as this became apparent, our developers started applying changes via SSMS and now don't check in their changes to source control. This is just a complete mess and if we had known this would be such a problem, we would not have upgraded to SQL 12 at all. You may say that well, that's the VS team, but if the two teams aren't on the same page and playing nicely together, one will suffer for the other's incompetence.