How to do RCA (Root Cause analysis)

Question

How to do RCA (Root Cause analysis)

Simha24

SSCommitted

Points: 1984
More actions
April 30, 2012 at 1:39 am

#268001

Hi....
I have a 4 Reference SQL Server box which are running On SP3.
In Some node overs SQL Server Management studio version is showing Lower(1399) version.
Due which i am unable to create mantanace plans.
My boss asking me to do RCA on it.
How can i get these details in detailed.
Like.
1. How many times version got upgraded and where it was missed.
2. why Other client tools are not upgraded like other nodes.
Stats on my Nodes:
NodeName Engine Version Client Version
NODE1 9.0.4035 9.00.4035.00
NODE2 9.0.4035 9.00.4035.00
NODE3 9.0.4035 9.00.1399.00
NODE4 9.0.4035 9.00.1399.00
I have an issue with NODE3 and NODE4.

Viewing 10 posts - 1 through 9 (of 9 total)

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

Schadenfreude-Mei SSChampion Points: 14083 More actions · Answer 1

Simha24 (4/30/2012)
Hi....
I have a 4 Reference SQL Server box which are running On SP3.
In Some node overs SQL Server Management studio version is showing Lower(1399) version.
Due which i am unable to create mantanace plans.
My boss asking me to do RCA on it.
How can i get these details in detailed.
Like.
1. How many times version got upgraded and where it was missed.
2. why Other client tools are not upgraded like other nodes.
Stats on my Nodes:
NodeName Engine Version Client Version
NODE1 9.0.4230 9.00.4035.00
NODE2 9.0.4035 9.00.4035.00
NODE3 9.0.4230 9.00.1399.00
NODE4 9.0.4230 9.00.1399.00
I have an issue with NODE3 and NODE4.

For a start .1399 is RTM! I have literally only just posted on someone elses thread on virtually the same question.

So you have two instaces on SP3 and 2 on RTM. Assuming you have gone SP1,2,3 something has gone really wrong cause 2 nodes never got updated. TBH, shame on you for even allowing and RTM server instance to slip the net. SP1 was released at the same time as RTM so even MS knew RTM was cack.

As far as what got updated and when, you would need to look at your procedures and ask your network guys. We have had issues here where WSUS releases to a server and not others. But again TBH you shouldnt be allowing WSUS to touch live SQL boxes.

Either way, the info you speak of can be found in the WIndows update log, though youll likely have to cross-ref with MS to identify KB-numbers.

HTH

Adam Zacks-------------------------------------------Be Nice, Or Leave

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 2

Schadenfreude-Mei (4/30/2012)
SP1 was released at the same time as RTM so even MS knew RTM was cack.

SQL 2005 RTM was released November 2005

SQL 2005 SP1 was released March 2006

The main thing that SP1 included was database mirroring (not in RTM because it was deemed insufficiently tested)

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Schadenfreude-Mei SSChampion Points: 14083 More actions · Answer 3

GilaMonster (4/30/2012)
Schadenfreude-Mei (4/30/2012)
SP1 was released at the same time as RTM so even MS knew RTM was cack.
SQL 2005 RTM was released November 2005
SQL 2005 SP1 was released March 2006
The main thing that SP1 included was database mirroring (not in RTM because it was deemed insufficiently tested)

My appologies, I stand corrected.

Adam Zacks-------------------------------------------Be Nice, Or Leave

Simha24 SSCommitted Points: 1984 More actions · Answer 4

Hi Gail ,

In my CASE, All SQL Sever engine versions are same (4 nodes are running with SP3) where as client tools on 2 Nodes are running with RTM version.

Even same details are showing in Registey.

How can i upgrade other lower version clients to SP3(because i have an issue while creating mantenance plan)

Lowell SSC Guru Points: 323518 More actions · Answer 5

Simha24 (4/30/2012)
Hi Gail ,
In my CASE, All SQL Sever engine versions are same (4 nodes are running with SP3) where as client tools on 2 Nodes are running with RTM version.
Even same details are showing in Registey.
How can i upgrade other lower version clients to SP3(because i have an issue while creating mantenance plan)

you are stating that they are all teh same version now? That directly contradicts what you posted in the first part:

Stats on my Nodes:
NodeName Engine Version
NODE1 9.0.4230
NODE2 9.0.4035
NODE3 9.0.4230
NODE4 9.0.4230

Edit: people are reading the client version you posted, not the engine version.

Node 2 is behind the other 3 nodes, isn't it?

What is preventing you from re-running the Service Packs on nodes 2 ? Did you get an error before? could nodes 2 have upgraded other instances on them, instead of the instances participating in the cluster?

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!

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 6

Simha24 (4/30/2012)
How can i upgrade other lower version clients to SP3(because i have an issue while creating mantenance plan)

Run SP3 on those instances and select the client tools to patch.

That said, you shouldn't be using client tools that are loaded onto a server to do things like maint plans. Use your own machine for that.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Simha24 SSCommitted Points: 1984 More actions · Answer 7

Simha24

SSCommitted

Points: 1984

April 30, 2012 at 7:43 am

#1481242

Thanks for all

curious_sqldba SSC-Dedicated Points: 36494 More actions · Answer 8

Simha24 (4/30/2012)
Thanks for all

Hope you have resolved your issue. You can also refer to "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG" for detail logs as to your RCA.

Nadrek SSC-Insane Points: 20039 More actions · Answer 9

For SQL 2005 in specific, note that build 5292 addresses MS11-049, which is a security update. You may want to look into upgrading to this build level as well, depending on your organization's stance on security based patching.