I’m going to move to 2012 version of both Visual Studio and SQL Server.
Hence, I have a question related to comparison of VS2012 and SSMS 2012.
First-of-all, I’ve read the topic «Why should I use Visual Studio 2010 over SSMS for my database development?», but since they are talking about 2010, I would like to focus on new 2012 version.
My questions:
-
What exactly the difference between Visual Studio 2012 and SQL Server Management Studio 2012 in the aspect of SQL Server & DB management?
-
What is the gap, what can I do in SSMS 2012, that is not possible in VS 2012?
Particularly if I’m talking about the basic level of DB-creation & maintenance, should I install SSMS or is VS quite enough.
Personally I’d go with both, but I’m a DBA who is more focused on management-centric workflows. I’m less familiar with using VS as a SQL Server management interface, but looking at it, it looks as if you can do many things in VS that you can do in SSMS, but there are also many things you cannot do.
If you want to monitor replication subscriptions and other agent-based jobs, your life will be much easier with SSMS installed. Essential (and more advanced) DBA tasks are more readily facilitated by SSMS. Disaster Recovery, Replication, SQL Server Agent, Service Control, etc. These are all reasons to include SSMS.
They are not competitors, but tools created with specific purposes. If your job description dictates that both tools would streamline your workflow then by all means install both.