Solved

Upgrade from SQL 2000 SP4 to SQL 2008 R2

Posted on 2011-09-13
6
327 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 82

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
Control application downtime with dependency maps

Visualize the interdependencies between application components better with Applications Manager's automated application discovery and dependency mapping feature. Resolve performance issues faster by quickly isolating problematic components.

 
LVL 82

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 38

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

What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

Join & Write a Comment

Suggested Solutions

This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
Slowly Changing Dimension Transformation component in data task flow is very useful for us to manage and control how data changes in SSIS.
Via a live example, show how to extract information from SQL Server on Database, Connection and Server properties
Viewers will learn how to use the UPDATE and DELETE statements to change or remove existing data from their tables. Make a table: Update a specific column given a specific row using the UPDATE statement: Remove a set of values using the DELETE s…

758 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

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now