![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a particularily annoying upgrade that I'm forced to do on two of our test servers. One in particular has our MSSQL test databases on it... The OS is currently Windows 2000 Professional with 3 instances of MSSQL running on it (3 databases). We are upgrading all test servers to Windows Server 2003 Standard and I cannot just upgrade the OS, I'm forced to do a clean install. My current plan is to boot from the Server 2003 CD and install the OS in place over the existing OS. If I just re-install MSSQL into the existing directory and setup the databases with correct names, will the new MSSQL install pickup the existing data? Plan B is to do a Database "move" to another machine, upgrade the OS, and then do a "move-back" to complete the upgrade. Is plan A impossible? Is plan B better? Is there some other way to do it that I just don't see right now? Thanks in advance. -Jay |
#3
| |||
| |||
|
|
Don´t know how important the data is to you, |
|
but I would prefer option C, to backup and restore the database files, to keep the databases consistent. |
|
Another way woud be to detach and attach the DBs |
#4
| |||
| |||
|
|
Don´t know how important the data is to you, It is a test database, we have backups from a couple days ago. but I would prefer option C, to backup and restore the database files, to keep the databases consistent. How is this different from B? Another way woud be to detach and attach the DBs This sounds like the solution that would use the smallest amount of time. Is there a good step-by-step guide for how to do it? (Sorry if I'm a bit clueless, this isn't normally my area of expertise). -- Jay [ i/o] |
#5
| |||
| |||
|
|
For more information on sp_attach_db, please visit |
![]() |
| Thread Tools | |
| Display Modes | |
| |