Resource Database is not upgraded when SP or CU is applied to SQL2005 failover cluster running on Windows 2008 - by qcjamess

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 532372 Comments
Status Closed Workarounds
Type Bug Repros 7
Opened 2/9/2010 3:29:47 PM
Access Restriction Public


the resource database does not get properly upgraded on a SQL 2005 failover cluster running on Windows 2008.  This only occurs if the hostnames of the physical nodes are lower case.  

Please see for specific details

The 'workaround' specified in the above linked article does not always work and is dangerous to perform on a production environment.
Sign in to post a comment.
Posted by Rob Casillas on 4/27/2010 at 8:16 PM
Per KB978308, this issue is corrected in SP3 CU9. Correct?
Posted by Microsoft on 3/12/2010 at 11:53 AM
This is an issue that applies to SQL Server 2005, and it is not applicable to newer versions of SQL Server.

Since for SQL Server 2005, there is no way to slipstream a fix pro-actively, user will run into this issue for this configuration (where machine names are lower case or mixed case). This is not avoidable unless machine names are set to be uppercase from the very beginning.

Once this issue is hit, the only workaround is as publicly documented and supported by SQL Server CSS in:
Posted by Microsoft on 3/4/2010 at 3:02 PM
Thank you for bringing this to our attention. We will look more closely into the scenario to ensure there are no more serious downstream effects, and move towards eliminating this issue in the next major release / PCU / CU.
Posted by Microsoft on 2/12/2010 at 1:24 PM
Thank you for posting this behavior, we will investigate why the versions are not remaining consistent after the SP3 upgrade.
Posted by qcjamess on 2/9/2010 at 3:53 PM
It appears that this issue can be reproduced with Windows 2003 R2 clusters also