Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
aiken
Aged Yak Warrior
525 Posts |
 Posted - 2002-08-27 : 12:24:30
|
| At long last, we're going to be upgrading our fairly antiquated DB server (NT 4, dual PIII-450's).The RAID array that our production database and log file is on will remain the same, just be moved to another, more modern server. The system RAID, where master, model, and msdb live, will not be making the move.Can anyone give me some advice, or point me to an article, about this kind of move? For our production database, a simple detach/attach should work fine. However, how do I go about getting our various jobs and such across? Detach/detach MSDB doesn't sound like it would work, and I really don't want to have to re-create all of those jobs (maybe 25 jobs with an average of 8-10 steps).Thanks for any advice-b |
|
|
smccreadie
Aged Yak Warrior
505 Posts |
Posted - 2002-08-27 : 12:51:20
|
| There was a recent article on moving from SQL7 -> 2000. (http://www.sqlteam.com/item.asp?ItemID=9066).Many of the same principles apply for moving to a new box. |
 |
|
|
|
|
|
Moving production DB and jobs to new hardware?