May 29, 2012 at 10:53 am
Hi DBA's
Please suggest me for patching SQL 2000 server.
This server is more fragile and old. I need to patch it, suggest me if there are any pracautions to be taken before patching it.
Windows Derails
Microsoft Windowd 2003
Enterprise x64 Edition
Service Pack 2
SQLServer Details
Microsoft SQL Server 2000 - 8.00.2055 (Intel X86) Oct 16 2008 15:48:13 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3791: Service Pack 2)
Thanks in advance!
May 29, 2012 at 2:36 pm
This is a 2008 forum. You will have better luck getting responses if you post to the proper forum.
Jared
CE - Microsoft
May 29, 2012 at 3:03 pm
Back up everything. Are you looking to patch Windows, SQL, or both? What patches?
I wouldn't call SQL 2000 old or fragile.
If you're really worried, I'd do a P2V migration and keep the VM around. If nothing else, it would give you a test environment for the patches, or a DR instance to keep around.
Editor: moved to SQL 2000
May 29, 2012 at 3:07 pm
Patching both OS and SQL Server.
I want to patch SP4 on SQL Server
Thanks for the reply!
May 29, 2012 at 3:12 pm
you are welcome.
SP4 is pretty stable, and should be fine. Note that there are some post-SP4 patches that you might want to apply as well as a few are security items.
May 29, 2012 at 4:03 pm
if you mean you want to apply SP4 that is already applied, SP4 is version 8.00.2039.
If you are going to patch SQL:
make sure you have backups of all databases but in particular the system databases
stop SQL before the install and take flat file copies of the system database files
make sure any apps that connect are stopped before you start
if in the worst case scenario you have to reinstall SQL:
make sure you have copies of the software to get back to the current version if the patch fails
make sure you know the service account SQL is running under and its password
make sure you know the install directories so you can reinstall to the same directories if needed
for belt and braces protection script out or note as much server detail as possible, i.e. logins with default databases and language, sQLagent jobs, sp_configure, database locations, DTS packages.
---------------------------------------------------------------------
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply