2k5 SP1 upgrade software is showing different current versions depending on which node it is ran from -- sql server clustering

Michael Abair
10/18/2007 10:08:40 AM

We have updated multiple instances of sql server 2k5 EE to SP1 and oddly
enough some of them still show that they are at
RTM version 9.00.1399.06 instead of 9.00.2156.00. when checking through ssms
and select @@version

When we run SP1 against it to see the instances it recommends for an update
on one cluster node it shows
all of the versions as being updated and on other nodes it shows
discrepancies.
some of the instances that select @@version shows as being updated although
they are not preselected for the update they
are showing up in the list as being the RTM version 1399 as well.

Has anyone had a similar experience with updating Sql Server 2005 instances?
I know there used to be some buggyness in 2000 in regards to version numbers
but I haven't seen any reports of this in 2k5.
Any help would be appreciated.

Geoff N. Hiten
10/18/2007 10:20:04 AM

Is this for the SQL engine or for some non-engine components?

Unlike SQL 2000, the SQL 2005 installer does not update all components
cluster-wide. Only SQL Server, SQL Agent, and SQL Analysis Services get
updated cluster-wide. Everything else must be updated locally on each node.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

[quoted text, click to view]

Michael Abair
10/18/2007 11:18:05 AM

This is the sql server engine itself not the tools thus the select @@version
results.

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about sql server clustering

sql server clustering : 2k5 SP1 upgrade software is showing different current versions depending on which node it is ran from