April 30, 2010 at 3:13 pm
Hi,
We have clustered SQL Server 2005 instance and want upgrade to SQL Server 2008 using in-place upgrade method. The current SQL Server 2005 instance name is SQL1VS1\INS1. Now while upgrading what should we give, when the setup asks for Instance ID in the Instance ID box? From the failover document SQLServer2008FailoverCluster, it says NOT to use nondefault values for the Instance ID. Waht happens if we use nondefault Instance ID name?
Typical stand-alone instances of SQL Server 2008, whether default or named instances, do not use a nondefault value for the Instance ID box
Thank you
May 1, 2010 at 9:00 am
Hi,
Did you read that from:
http://msdn.microsoft.com/en-us/library/bb500433.aspx ?
I don't believe that MS is saying not to use a named instance, I think they are just saying that most instance installations use the default instance instead. I'm not aware of any issues of using a named instance aside from possibly needing to specify the slash and instance name in your connection strings.
Andrew
May 3, 2010 at 12:30 pm
Did you read that from:
http://msdn.microsoft.com/en-us/library/bb500433.aspx ?
I don't believe that MS is saying not to use a named instance, I think they are just saying that most instance installations use the default instance instead. I'm not aware of any issues of using a named instance aside from possibly needing to specify the slash and instance name in your connection strings
My question is regarding the INSTANCE ID not the named instance name
thanks
May 3, 2010 at 1:07 pm
Sorry about that Mani, I guess I read your post too quickly. I don't know the answer to that. SQL Server builds it's directory structure and registry entries from the InstanceID name (ie instance name INS1 would install to the "..\Microsoft SQL Server\MSSQL10.INS1\" folder as well as making any registry entries that referenced this Instance ID). Doing an in place upgrade with a new InstanceID, I assume it would install 2008 to the new folder and would use use the new instance name for any registry values. I assume this would function properly, but would be a little disconjointed for someone trying to figure out what instance name maps to which set of binaries and registry values.
Out of curiosity, what prompted you to consider making this change? If you decide to do so, I'd be interested to hear the outcome (just make sure you try it on a dev system first š ).
Andrew
January 18, 2011 at 3:53 pm
I just ran across the same note; however, the recommendation is listed under "Install A SQL Server 2k8 Failover Cluster Using Integrated Installation with Add Node Operation".
Although it was not mentioned during an upgrade cluster process, the disjointed reference may have some merit? It does mention a preivous installed instance????
January 18, 2011 at 4:01 pm
Read-on and discovered that the āInstance Nameā is used as the default "Instance ID".
Iām guessing that this is just a best practice as changing the default ID may cause confusion - thus disjointing the ID from the actual Instance Name installation directories.
January 18, 2011 at 4:02 pm
Read-on and discovered that the āInstance Nameā is used as the default "Instance ID".
Iām guessing that this is just a best practice as changing the default ID may cause confusion - thus disjointing the ID from the actual Instance Name installation directories.
July 30, 2015 at 6:09 am
Sorry for jumping on your post, but I was getting a little confused reading it myself.
I have named instances of SQL 2012 and the Instance ID is null, which seems to me as odd, since Microsoft has a number for everything.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply