SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server Patching


SQL Server Patching

Author
Message
sivaprasad
sivaprasad
SSCrazy
SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)

Group: General Forum Members
Points: 2857 Visits: 269
My client has around 200 SQL Server instances running on SQL Server 2000, 2005 and 2008. We have agreement to apply the patching of the SQL Server Instances Quarterly.

The question here is there are some SQL Server 2000 instances running on SP4 with version 8.00.2039. On these SQL Server 2000 instance, client not interested on upgrading it. However client asks to apply any patching on it.

1. Is there any mandatory hotfixes exists for SQL Server 2000 running on SP4?
2. How do we know and where can we find if any mandatory patch or hotfixe exists for SQL Server 2000, 2005 and 2008?
3. I have collected the detail across the web, is that below details correct?


SQL Server Build Version Patch Level
===================================================

SQL Server 2000 8.00.2039 2000 SP4
SQL Server 2005 9.00.4226 2005 SP3+Q970279 (Cumulative HF 4)
SQL Server 2008 10.00.2714 2008 + Cumulative Update 2 for SP1
===================================================

Is there any specific Patch level, do we have to maintain SQL Server 2000, 2005 to upgrade to SQL Server 2005 or 2008?

Is the Microsoft support based on SQL Server version running at Service Pack level or specified patch level?

Sivaprasad S - [ SIVA ]http://sivasql.blogspot.com/
add2700
add2700
SSC Veteran
SSC Veteran (212 reputation)SSC Veteran (212 reputation)SSC Veteran (212 reputation)SSC Veteran (212 reputation)SSC Veteran (212 reputation)SSC Veteran (212 reputation)SSC Veteran (212 reputation)SSC Veteran (212 reputation)

Group: General Forum Members
Points: 212 Visits: 234
All the info you need is a google search away.

http://www.sqlservercentral.com/articles/Administration/2987/
http://msdn.microsoft.com/en-us/library/ms144256(SQL.90).aspx

Of course ideally you'd want a dev environment to upgrade and test it.

As for latest patches, some people say don't patch unless there's a security or functionality issue.

Others say always patch. I don't have enough experience to say either way, although I patch my learning box often.
GabyYYZ
GabyYYZ
SSCrazy
SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)

Group: General Forum Members
Points: 2943 Visits: 2336
add2700 (7/27/2009)
All the info you need is a google search away.

http://www.sqlservercentral.com/articles/Administration/2987/
http://msdn.microsoft.com/en-us/library/ms144256(SQL.90).aspx

Of course ideally you'd want a dev environment to upgrade and test it.

As for latest patches, some people say don't patch unless there's a security or functionality issue.

Others say always patch. I don't have enough experience to say either way, although I patch my learning box often.

Having recently update 250+ stores (about 5-6 a day off and on for 2 months), there is no easy way to do this. Generate your list, divide and conquer if there is another DBA with you, and once the 2005/2008 are patched, get into a schedule where every X months, patch the dev and qa boxes, test, and if all is okay, continue patching to production a week or so later. Regarding 2000, just go for SP4 + latest hotfix (2282 I think). SQL 2000 is at end of life anyways for support, so you might as well go for the most recent and possibly last hotfix released.

Gaby
________________________________________________________________
"In theory, theory and practice are the same. In practice, they are not."
- Albert Einstein

tdietrich
tdietrich
SSC-Enthusiastic
SSC-Enthusiastic (167 reputation)SSC-Enthusiastic (167 reputation)SSC-Enthusiastic (167 reputation)SSC-Enthusiastic (167 reputation)SSC-Enthusiastic (167 reputation)SSC-Enthusiastic (167 reputation)SSC-Enthusiastic (167 reputation)SSC-Enthusiastic (167 reputation)

Group: General Forum Members
Points: 167 Visits: 80
For SQL 2000, there was actually a Security Vulnerability published in April and republished in August. MS12-060. Microsoft released hotfix version 8.00.2305. If you are going to patch your SQL 2000 SP4 servers, I would put this one on.

We have over 1000 SQL servers installed with a mix of SQL 2000, 2005, 2008, 2008 R2, and 2012.

This is my favorite site for tracking the latest SQL versions:
http://sqlserverbuilds.blogspot.com/
They do a pretty good job of keeping this list up to date - and they provide links directly to the download for each version.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum







































































































































































SQLServerCentral


Search