Multiple SQL Server version instances on same machine, caveats??

Question

Post reply

Multiple SQL Server version instances on same machine, caveats??

codenamesql

SSC Veteran

Points: 274
More actions
March 29, 2014 at 12:05 pm

#396497

Hi guys,
A little background blathering:
I understand that different versions (an even different sp's) may be installed on the same machine but I am concerned that I may be pushing the envelope and possibly introducing issues. I really don't want to have to swap images and prefer to start/stop the various servers as necessary if they won't conflict with each other or introduce problems (of which I am unaware and obviously need such awareness).
I'm in QA and most of my testing has been limited to SQL Server 2008. I need to set up a code testing environment here at home (code only, stress testing not an issue here) and have purchased DEV editions of 2005, 2008, 2008R2, 2012 and will be adding 2014 later.
Will ALL of these play nice together on one machine?
Should they to be installed in specific order?
My intention is to install the SQL Servers as named instances on a Win7 pro machine (though I could bite the bullet and go with Server if absolutely necessary). I'll be connecting to the servers from a separate PC on the lan.
Performance isn't an issue as this is primarily for initial testing of .net interoperability code with the more stringent testing to be performed in a production similar environment.
So, caveats? Tips/tricks? Suggestions for sanity retention? :w00t:
Thanks in advance.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Eirikur Eiriksson SSC Guru Points: 182912 More actions · Answer 1

I have 2008R2, 2012 and 2014 on the same W7, all named instances, no problem 🙂

george sibbald SSC Guru Points: 104210 More actions · Answer 2

you can only have one instance of SSIS per machine, so whether that wide a range of versions would work happily I'm not sure.

---------------------------------------------------------------------

Shawn Melton SSC-Insane Points: 24685 More actions · Answer 3

A few links to review.

Multiple Versions

SSIS Coexistence

Each component (SSRS, SSIS, SSAS, and Database Engine) are all services so the different versions can coexist on the same machine. You can look through similar documentation as above on BOL to determine what shared components will only be for the latest version. This may or may not have any affect on your development.

My suggestion is start with the latest version first and go backward. The main point of doing this is because of the Visual Studio shell that will be installed for the shared components. VS 2010 is used for SSMS 2012 and SSDT, I believe 2014 will use the same thing. SQL Server 2008 will use VS 2008 and SQL Server 2005 VS2005. I have had the Visual Studio shells break going from 2005 and up.

I would also ensure once you have the version installed make sure it is patched to current build (all shared components as well, e.g. Visual Studio 2010).

Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton

SQLBuddy123 One Orange Chip Points: 28294 More actions · Answer 4

codenamesql (3/29/2014)
Hi guys,
A little background blathering:
I understand that different versions (an even different sp's) may be installed on the same machine but I am concerned that I may be pushing the envelope and possibly introducing issues. I really don't want to have to swap images and prefer to start/stop the various servers as necessary if they won't conflict with each other or introduce problems (of which I am unaware and obviously need such awareness).
I'm in QA and most of my testing has been limited to SQL Server 2008. I need to set up a code testing environment here at home (code only, stress testing not an issue here) and have purchased DEV editions of 2005, 2008, 2008R2, 2012 and will be adding 2014 later.
Will ALL of these play nice together on one machine?
Should they to be installed in specific order?
My intention is to install the SQL Servers as named instances on a Win7 pro machine (though I could bite the bullet and go with Server if absolutely necessary). I'll be connecting to the servers from a separate PC on the lan.
Performance isn't an issue as this is primarily for initial testing of .net interoperability code with the more stringent testing to be performed in a production similar environment.
So, caveats? Tips/tricks? Suggestions for sanity retention? :w00t:
Thanks in advance.

Start with SQL 2005 and then go forward with other installations. Sometimes Higher versions gives you a hard time installing older versions of SQL.

--

SQLBuddy

codenamesql SSC Veteran Points: 274 More actions · Answer 5

Thanks everyone. I'm ready to rock. Seems SSIS can be a somewhat tricky and it also seems a strange one-off integration compared to the other major modules. There must be a reason for that. At any rate I think I'll be okay for intended purpose. If not, I'll sacrifice a chicken and start over with a mission.. 🙂

Eirikur Eiriksson SSC Guru Points: 182912 More actions · Answer 6

Start with SQL 2005 and then go forward with other installations. Sometimes Higher versions gives you a hard time installing older versions of SQL.
--
SQLBuddy

I agree, start with the earliest version and install later versions in the version order. Never had any problems doing it this way ( obviously applies to more than just installing SQL Server, earlier versions are still troublesome 😀 )