Determining Build number when service is NOT running

Question

Determining Build number when service is NOT running

Jeff_aMagnumDBA

SSChasing Mays

Points: 625
More actions
February 19, 2010 at 10:04 am

#138289

I working in a 4 node, 4 instance, active/active SQL Server cluster and I need to figure out the what build I'm up to in the instances that are inactive on an active node. Each sqlserver/box is x64.
I have 4 nodes in the cluster, one instance of SQL is active on each node. Each node is a possible failover destination for any of the three other SQL instances.
All of my instances are supposed to be up to 2005 SP2 CU10 (9.0.3294). Looks like the registry is only updated when an SP is installed as all of the instances show 3042 (SP2) in the Registry, even the instances that are running and I can see are SP2 CU10 via xp_msver.
So is there anyway to tell the current build of a particular instance number when that instance is NOT running?
Failing each instance to each possible node and determining build number is not an option as each instance is prod.
I'm researching an issue in which it looks like one of the instances on one of my nodes didn't get upgraded, so I need to verify that. But a legit solution here would help anybody in a clustered environment verify upgrades after they are applied.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

GSquared SSC Guru Points: 260824 More actions · Answer 1

The only thing I can think of is checking the update history. If you open Windows Update, you can get a fully history of installed updates. There may be a way to query that, but I don't know what it would be.

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

Lowell SSC Guru Points: 323518 More actions · Answer 2

which registry key are you looking at?

on my machine, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\CurrentVersion

has a value of CurrentVersion=10.0.1600.22

for the the FileVersion of sqlservr.exe, i had 2 on my machine, one for an 2005 express version(2005.90.3042.0) , and another for a version 10 version ;(2007.100.1600.22)

does that help at all?

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Jeff_aMagnumDBA SSChasing Mays Points: 625 More actions · Answer 3

I do see the hotfix as installed when I look in Add/Remove Programs.

Jeff_aMagnumDBA SSChasing Mays Points: 625 More actions · Answer 4

My registry looks a little different. Each instance is listed in the tree, but under each instance is an attribute called "CurrentVersion", for all instances this value is 9.0.3042, even for the active instance where I can query in T-SQL and see that its really at 9.0.3294 (@@version or xp_msver)

I'm combing thru the instal logs for the hotfix now. Something had to have gone wrong in that process and been logged.

Even now it seems stupid to think that i could have two different "versions" of SQL on the box.

But I saw it w/ my own two eyes. I had two instances on one node, one instance @ 3042, the other at 3294. I've since failed the 3042 back to its home node so I can't produce that proof.