Nowadays, monitoring is a mixture of tools, systems, and codes—making it a very complex process. And with this complexity, comes variables for failure. Get DZone’s new Guide to Performance to learn how to proactively find these variables and solve them before a disruption occurs.
Solved
Upgrade from SQL 2000 SP4 to SQL 2008 R2
Posted on 2011-09-13
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?
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?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2
2
- +1
6 Comments
Active today
Windows 2008 R2 is 64-bit only. Will your hardware support it? The drivers for applications will also have to be upgraded.
Active today
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.
Active today
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.
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.
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.
Featured Post
Read this Gartner Research Note and discover how your IT organization can automate and optimize DevOps processes using a toolchain architecture.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
How to leverage one TLS certificate to encrypt Microsoft SQL traffic and Remote Desktop Services, versus creating multiple tickets for the same server.
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.
Familiarize people with the process of retrieving data from SQL Server using an Access pass-thru query. Microsoft Access is a very powerful client/server development tool. One of the ways that you can retrieve data from a SQL Server is by using a pa…
Viewers will learn how to use the SELECT statement in SQL to return specific rows and columns, with various degrees of sorting and limits in place.
Suggested Courses
Course of the Month8 days, 16 hours left to enroll
734 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.