SQL Server 2008 version confusion
-
I have 4 SQL Servers in my environment, SQL1, SQL2, SQL 3 and SQL4.
SQL1 & SQL 2 are part of of Windows 2008 R2 Cluster.
SQL3 is my test SQL Server
SQL4 is my DR SQL Server.
SQL2,3 and 4 are currently at release 10.2.4311.
SQL1 is at 10.2.4064
Since SQL1 and SQL2 are in a cluster, whenever I failover SQL goes into "Script Update Mode" for about 2 minutes since the servers are at different releases.
It seems like SQL1 has an extra patch which causes its release to be at 4064. The patch is "GDR 4064 for SQL Server 2008 (KB2494089)". This KB also seems linked to KB2494094.
MS11-49 seems to be the update and it has multiple releases (GDR, QFE..) which cause SQL to be at a different releases depending on which version was applied.
My other question is why if SQL1 has an extra patch/hotfix, why is it at a lower release of SQL (4064) then the nodes that dont have the patch installed (4311).
Is it best to just uninstall GDR 4064 from SQL1 to level set all Nodes?
I found a donwload for GDR 4064 but if I try to apply it to any of the SQL nodes running 4311, it tells me I cant because I am at a higher release so how this got install on SQL1 is a mystery. Any help would be appreciated.
-
Where are you getting this information from? There is no 10.2.XXX Only 10.00.XXXX (2008) and 10.50.XXXX (2008 R2).
Jared
CE - Microsoft -
robert.tuniewicz (6/26/2012)
I have 4 SQL Servers in my environment, SQL1, SQL2, SQL 3 and SQL4.SQL1 & SQL 2 are part of of Windows 2008 R2 Cluster.
SQL3 is my test SQL Server
SQL4 is my DR SQL Server.
SQL2,3 and 4 are currently at release 10.2.4311.
SQL1 is at 10.2.4064
Since SQL1 and SQL2 are in a cluster, whenever I failover SQL goes into "Script Update Mode" for about 2 minutes since the servers are at different releases.
It seems like SQL1 has an extra patch which causes its release to be at 4064. The patch is "GDR 4064 for SQL Server 2008 (KB2494089)". This KB also seems linked to KB2494094.
MS11-49 seems to be the update and it has multiple releases (GDR, QFE..) which cause SQL to be at a different releases depending on which version was applied.
My other question is why if SQL1 has an extra patch/hotfix, why is it at a lower release of SQL (4064) then the nodes that dont have the patch installed (4311).
Is it best to just uninstall GDR 4064 from SQL1 to level set all Nodes?
I found a donwload for GDR 4064 but if I try to apply it to any of the SQL nodes running 4311, it tells me I cant because I am at a higher release so how this got install on SQL1 is a mystery. Any help would be appreciated.
I suspect you meant 10.00 and not 10.2. According to http://sqlserverbuilds.blogspot.com[/url] version 10.00.4064 is SP2RTM+MS11-049:
Build 10.00.4311 is between SP2+CU4 and CU5. So, the question becomes, how did SQL2 get CU4, and SQL1 did not?
Consider applying CU4 and MS11-049 to SQL1.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato -
Your right, If I open SQL Management Studio it shows the version as 10.0.4311 (or 4064). If you go into Add/Remove Programs - View Installed Updates, it shows version numbers as 10.2.4311 (or 4064).
On SQL1, the following patches are listed as installed for MS SQL Server 2008 (64 Bit)
Hotfix 4311 for SQL Server 2008 (KB2494094)
GDR 4064 for SQL Server 2008 (KB2494089)
Service Pack 2 for SQL Server 2008 (KB2285068)
On SQL2, installed patches look like this:
Hotfix 4311 for SQL Server 2008 (KB2494094)
Service Pack 2 for SQL Server 2008 (KB2285068)
Notice GDR 4064 is missing on SQL2. If I try to install GDR 4064, it tells me I cant since I am at 4311. The presence of GDR 4064 causes SQL to read the version as 10.0.4064. On SQL 2, the version displays as 10.0.4311.
-
Yeah, on 1 somebody applied a hotfix and not an update. I would work on getting them both to a "update" version, not removing a hotfix from 1.
Jared
CE - Microsoft -
So GDR 4064 is a Hotfix?
-
Can you please post the results of this from all 4 instances, so we're all on the same page?
SELECT SERVERPROPERTY('Edition') AS Edition,SERVERPROPERTY('ProductVersion') AS ProductVersion,
SERVERPROPERTY('ProductLevel') AS ProductLevel
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato -
No the 4311 is, but it is not cumulative. So you installed that on server1 (hotfixes are installed independently from CUs) before the cumulative updates were installed. I was hoping you could install a later cumulative update greater than 4311. I mean, in a perfect world... you should upgrade all the way to Service Pack 3, CU5. See this link below:
http://sqlserverbuilds.blogspot.com/
Jared
CE - Microsoft -
The result of that query is:
SQL2, 3 and 4
Edition: Enterprise Edition 64bit
Product/Version: 10.0.4311
ProductLevel: SP2
on SQL1
Edition: Enterprise Edition 64bit
Product/Version: 10.0.4064
ProductLevel: SP2
SQL1 and 2 are in a cluster. So when I failover between them I get the "Script Update Mode" message. I want to at the very least get both these instances running at 4311. Based on a previous post, the best way to do this is to upgrade both nodes to the next highest CU rather then go and uninstall GDR 4064 from SQL1.
I dont know how SQL1 got GDR 4064 and the other 3 nodes did not. However, since HotFix 4311 is installed on all nodes why does SQL1 not read its version as 4311.
-
robert.tuniewicz (6/26/2012)
The result of that query is:SQL2, 3 and 4
Edition: Enterprise Edition 64bit
Product/Version: 10.0.4311
ProductLevel: SP2
on SQL1
Edition: Enterprise Edition 64bit
Product/Version: 10.0.4064
ProductLevel: SP2
SQL1 and 2 are in a cluster. So when I failover between them I get the "Script Update Mode" message. I want to at the very least get both these instances running at 4311. Based on a previous post, the best way to do this is to upgrade both nodes to the next highest CU rather then go and uninstall GDR 4064 from SQL1.
I dont know how SQL1 got GDR 4064 and the other 3 nodes did not. However, since HotFix 4311 is installed on all nodes why does SQL1 not read its version as 4311.
Likely because hotfixes are not cumulative. Best I can guess is you have SP2+CU4+MS11-049 on SQL2, 3 and 4 & SP2+MS11-049 on SQL1. Look into applying CU4 on SQL1, and then the relevant version msi for MS11-049 on top of that.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply