Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I already have SQL Server 2008 R2 Developer edition on my laptop. One of the databases that we are using is SQL Server 2012. I can’t modify the stored procedures. I have to log onto the server to use Management Studio 2012. It is kind of a pain. Is it worth putting a named instance on my local machine to use Management Studio 2012? What sort of problems might I run into?
If you only want to install Management Studio 2012 on your local machine you can do that without having to add another instance. Just start the install and select only the management tools when you get to the feature selection.
I’m actually doing it myself as I wanted to take advantage of some of the improvements in SSMS 2012. We don’t have any production servers running 2012 yet, but I still do all my SSMS work in the 2012 version even on the older servers.
To answer your core question however, putting a second instance of a different version is fully supported by SQL. Microsoft doesn’t have a 2012 version of this article yet but the information is likely to be pretty much the same for gotcha’s and things to keep in mind about side by side installs.