February 5, 2008 at 10:37 am
Hello
We recently tried to upgrade a SQL 2k Cluster from SP3 to SP4. The cluster also has replicated DBs.
The SP4 did not complete successfully (as indicated by the logs), but if we do a select @@version , shows up as 8.00.2039 ? Appears that the system is in a transient state ..
We have also found what might be the possible causes for the failure and have fixed them.
Qn is would it be okay/safe to simply try and reinstall SP4 again ? Or do we need to unistall SP4 first ..?
has anyone run into this before or done it?
please advise ..
Thanks
February 5, 2008 at 2:46 pm
It can't do any harm to re-try the SP4 install, if SQL thinks it is complete already it simply won't do anything.
did the install bomb out? Did all the upgrade scripts run through.? Whats actually in the logs?
I have had a standalone server where the install went past the scripts did not complete with a 'successful' message but version came out ok as 2039. I could find nothing wrong so I allowed the server to run and it never gave me any problems.
Don't know your exact situation though so I am dubious about giving cast iron promises or recommendations.:unsure:
Be aware backout of SP4 is uninstall\reinstall which I guess you want to avoid.
---------------------------------------------------------------------
April 13, 2008 at 10:02 am
I think 2039 is the correct build number for SP4. I installed it recently, and the install itself seemed to go okay, both on the test server, and on the live server at the weekend.
When the live system came under load on Monday morning though, it was clear that it was struggling. I've written this up with some level of detail here:
http://websql.blogspot.com/2008/04/trials-and-tribulations-of-sql-server.html
I guess we might have suffered because it was a moderately big server, and we sufferered from some parallelism issues, and also the "more than 2GB of memory" problem. What seems to have worked for us so far is to install the hotfix rollup for SP4:
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply