SQL Server Home
Resource Database is not upgraded when SP or CU is applied to SQL2005 failover cluster running on Windows 2008
as Won't Fix
2/9/2010 3:29:47 PM
User(s) can reproduce this bug
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 http://blogs.msdn.com/sqlserverfaq/archive/2009/03/16/unable-to-create-maintenance-plans-after-service-pack-2-is-applied-on-sql-server-2005-fail-over-cluster-instance-running-on-windows-2008-cluster.aspx for specific details
The 'workaround' specified in the above linked article does not always work and is dangerous to perform on a production environment.
SQL Server 2005 - Enterprise Edition
Windows Server 2008
Operating System Language
Steps to Reproduce
1. create windows 2008 failover cluster, physical hostnames in lowercase
2. Install SQL 2005 failover cluster instance
3. Apply SQL 2005 SP3
4. check the version of the resource database with SELECT SERVERPROPERTY('ResourceVersion') command
The resource database version will not match the engine version. This causes issues with maintenance plans, database mail, database mirroring, and replication. Not only is the resource database mismatched, but several system stored procs are not updated as well. I suspect that the system stored procs that are not updated is the real issue here.
Several system stored procs and the resource database are not properly updated to the level of the SP or CU that is being applied.
We expect the SP or CU to be applied correctly, given that SQL 2005 SP3 is supported when installed on Windows 2008. This issue of having a lowercase hostname did not affect installations on Windows 2003 failover clusters. This problem only occurs when installing SQL 2005 on a Windows 2008 failover cluster that has physical hosts with lowercase (or mixed case) hostnames.
to post a comment.
Please enter a comment.
on 4/27/2010 at 8:16 PM
Per KB978308, this issue is corrected in SP3 CU9. Correct?
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:
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.
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.
on 2/9/2010 at 3:53 PM
It appears that this issue can be reproduced with Windows 2003 R2 clusters also http://sqlblog.com/blogs/ben_miller/archive/2010/01/11/long-time-sql-cluster-issue-resurfaced.aspx
to post a workaround.
Please enter a workaround.
© 2014 Microsoft