Solved

Upgrade from SQL 2000 SP4 to SQL 2008 R2

Posted on 2011-09-13
6
367 Views
Last Modified: 2012-05-12
I currently have a machine running SQL 2000 SP4 on Windows 2003 SP2 (32-bit). I want to upgrade an end up running SQL 2008 R2 on Windows 2008 R2.
Looking at the documentation as to what is supported, it seems like the upgrade path would be as follows:
1. Upgrade SQL to 2008 R2 in-place. I believe I would need to do this first since SQL 2000 SP4 is not supported on Windows 2003 so I cannot upgrade the operating system first.
2. Upgrade Windows to 2008 R2 in-place.

Has anyone done this? If so, what are the gotchas I should know about?
0
Comment
Question by:Julian123
6 Comments
 
LVL 83

Accepted Solution

by:
Dave Baldwin earned 500 total points
ID: 36534302
Windows 2008 R2 is 64-bit only.  Will your hardware support it?  The drivers for applications will also have to be upgraded.
0
 
LVL 12

Author Comment

by:Julian123
ID: 36534413
Sorry, I meant Windows 2008, the 32 bit version, not 2008 R2.
0
 
LVL 5

Expert Comment

by:Brian Chan
ID: 36534455
Can't do side-by-side upgrade?
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 83

Expert Comment

by:Dave Baldwin
ID: 36534473
I was wondering about that too.  For my own use, I never 'upgrade' a machine to another OS, I get a new machine to put it on and transfer my files and programs over.
0
 
LVL 39

Expert Comment

by:Aaron Tomosky
ID: 36534923
Agreed on never upgrading an os. Id also suggest skipping 2008 (vista based) and goin right to 2008 r2 ( win 7 based) if you don't have problems with having a 64bit os.

If you go this route, I would install SQL express on another box and try to import the database files. You can also connect to the sql2k db from the 2008r2 express ssms and make a backup that way. This way you can deal with SQL separately from the os.
0
 
LVL 5

Expert Comment

by:Brian Chan
ID: 36535231
Sometime it may be tough on budget or other limitation and that's understandable to be tempted to do it in-place. But, if you are doing it to a critial produciton environment, it is a clean cut to do it side-by-side as you still have the option to backout. Keep that in mind, MS is not going to be responsible for your data.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
Via a live example, show how to setup several different housekeeping processes for a SQL Server.

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question