Any known issues with adding a second instance of SQL Server 2005 to a server that already has an instance patched to SP3

I have a production server running SQL Server 2005 Enterprise Edition that has been patched up to SP3.

I had this problem in the past but never found the workaround, or I wasn't brave enough to go ahead and try it. I understand that I could do this on a test box and see what happens but I wanted to see if anyone had done this before and might save me the effort.

I need to put a second instance of SQL Server 2005 that will be a named instance. As it's going through the System Configuration Check I get the infamous "Edition Change Check (Warning) : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.".

I bypassed that and went ahead with the install. I'm pretty sure that there was just a check that found a different SQL Version and it assumed you were doing something with it instead of adding a new instance.

I just wanted to see if anyone knew of any issues and that I did things properly.

more ▼

asked Feb 23, 2010 at 03:34 PM in Default

Jason Crider gravatar image

Jason Crider
453 10 10 12

(comments are locked)
10|1200 characters needed characters left

2 answers: sort voted first

I have added secondary instances in the past after the fact. Each one patched to a different level. Have not seen any ill-effects from doing so. I did just the same as you described - continued past that warning.

more ▼

answered Feb 23, 2010 at 06:38 PM

CirqueDeSQLeil gravatar image

4.8k 10 11 15

Same here, though it was SQL Server Standard and SQL Server Express in my case. I will note that I have only ever done this on test or development boxes.
Feb 23, 2010 at 08:53 PM TimothyAWiseman
(comments are locked)
10|1200 characters needed characters left

The important thing to be aware of are non-instance aware services, like SSIS. If they are installed, don't add them to the new instance.

I would highly recommend that if you do this, you immediately patch the named instance back to the same level as the default instance. If you apply a CU that is post your default instance, apply that CU to the default as well.

This is the type of thing that should work, but I have seen quality issues in SQL 2000 with instances at times. I would not trust that all CUs properly deal with this and don't patch something that is potentially shared.

more ▼

answered Feb 23, 2010 at 10:10 PM

Steve Jones - Editor gravatar image

Steve Jones - Editor ♦♦
5.1k 78 79 82

(comments are locked)
10|1200 characters needed characters left
Your answer
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

New code box

There's a new way to format code on the site - the red speech bubble logo will automatically format T-SQL for you. The original code box is still there for XML, etc. More details here.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.



asked: Feb 23, 2010 at 03:34 PM

Seen: 1817 times

Last Updated: Feb 23, 2010 at 03:34 PM