September 25, 2008 at 9:03 am
I would like to install SP4 on our SQL Server 2000 SE SP3 Server. This is a test server. However, I was told it is a good practice to backup the following:
SQL Server Installation
Registry
SQL Server Databases
Are these three items important to back up and is there any other files which should be backed up?
Does a backup of the SQL Server Installation, means to make a copy of:
C:\Program Files\Microsoft SQL Server\80 and
C:\Program Files\Microsoft SQL Server\MSSQL?
What is a good tool\utility to use to copy the SQL Server Installation? Would something like XCopy be good to use?
What tool/utility can be used to make a copy of the Registry? Does the Registry have a single file name/location? If so, what is it?
Our SQL Server 2000 Environment:
Windows 2003 Server Rel 2 Standard Edition SP2
SQL Server 2000 Standard Edition SP3
Thanks in advance, Kevin
September 25, 2008 at 9:23 am
any copy would be sufficient(xcopy, copy/paste, drag/drop) for the sql installation files. And for the registry you can just open it with regedit and export. this will create file with all registry settings in it.
September 25, 2008 at 9:32 am
Registry: back up the Microsoft SQL Server node under HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft.
Installation: copy the SQL installation folder to a safe location, preferably on another machine or network share. You can get the installation folder by right-clicking on the instance name, selecting Properties, "Root Directory" entry under General tab.
System databases: copy the data and log files of the system databases to a safe location - you will need to stop SQL first.
Very important: take note of the location of the current system-db files and installation files.
If your upgrade fails, all you will have to do is copy your saved system-db files to the appropriate location, copy the installation files to the right location, and you are back to where you were before the upgrade.
Optionally, you can also back up your user databases, but a SQL upgrade should never be able to touch those.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply