![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have SQL 2000 x32 Standard installed on a X64 Win2K3 server. I'm trying to upgrade to SQL 2008 Standard. Both the Sys Config & Upgrade Advisor tools say I'm cleared for take off. However, when I try to upgrade, I get "there are no features selected for upgrade" under Select Features and I can't go any further. This is a first attempt and there are no previous bad or partial SQL 2K8 installs on this box. Is this happening because I'm attempting a cross-platform upgrade (X32 to X64)? If so and I can't do that, what is the best way to accomplish this upgrade? |
#3
| |||
| |||
|
|
morgan (morgan (AT) news (DOT) postalias) writes: I have SQL 2000 x32 Standard installed on a X64 Win2K3 server. I'm trying to upgrade to SQL 2008 Standard. Both the Sys Config & Upgrade Advisor tools say I'm cleared for take off. However, when I try to upgrade, I get "there are no features selected for upgrade" under Select Features and I can't go any further. This is a first attempt and there are no previous bad or partial SQL 2K8 installs on this box. Is this happening because I'm attempting a cross-platform upgrade (X32 to X64)? If so and I can't do that, what is the best way to accomplish this upgrade? Yes, there is no upgrade path between x86 and x64. One way is to install SQL 2008 as a named instance on the machine. You can then keep the SQL 2000 instance, and copy the databases with backup/restore to the SQL 2008. The advantage with this is that you can keep SQL 2000 as a reference, in case you have query that starts to perform badly on SQL 2008. (By the way, make sure that you update statistics when you migrate the database to SQL 2008, as all statistics are invalidated.) The drawback is that all clients will need to change so that they connect to the new server. You will also have to migrate logins and Agent jobs. The other option is to uninstall SQL 2000, and install SQL 2008 and reattach the user databases. Make sure to take a backup of master and msdb before you uninstall. You may be able to restore this on the new instance, but I have not tried this. If that works out, logins and jobs are automatically transferred. Yet an option is to find completely new hardware, and install SQL 2008 on that hardware, and the rename the machines, so clients does not have to change. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx . |
![]() |
| Thread Tools | |
| Display Modes | |
| |