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 |
|
CanadaDBA
583 Posts |
 Posted - 2008-09-03 : 12:37:19
|
| I am building some DR boxes and want to copy DBs, jobs, logins and everything from prod into initial DR box.For SQL 2000 I used to stop prod and copy whole System and User DBs physical files into new server on the same path. Then by running some small scripts, the new server was up and running. Of course both servers were identical from the partition point of view, Path, and SQL SPs, etc.This time I want to do the same work but with SQL 2005. I am not sure if the above solution works any more. If it doesn't, how can I implement the work?Thanks,Canada DBA |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-09-03 : 12:42:53
|
| You don't have to stop production for it. Are you looking for High availability or warm standby option? |
 |
|
|
CanadaDBA
583 Posts |
Posted - 2008-09-03 : 12:57:40
|
| At the moment I am just building an identical server. I want to have my SQL 2005 prod databases to be in DR. For SQL 2000 I used to stop the server to be able to copy mdf and ldf files, including master, msdb, and temdb. I copied the physical files from my SQL 2005 server and the files are in DR. But in the target server, I haven't replaced original files with the copy of production. I want to make sure the old trick can be done in 2005 as well.Canada DBA |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-09-03 : 22:05:15
|
| To be safe , I would do with Backup/Restore . |
|
|
|
|
|
|
|
|
Create identical SQL 2005 server