November 19, 2008 at 10:34 am
I have prod and test. I need to frequently replace test with prod and to do that I backup prod, then restore over test (and change the file names, database name, etc....).
However, it seems like COPY DATABASE would make life easier.
I could just drop a copy over test.
Also in the restore screen could I just select "prod" as the source to restore over top of "test" instead of backing up prod and restoring from the backup?
November 19, 2008 at 3:05 pm
Like all good answers, it depends...
the copy database wizard uses data pumps and takes longer, if I recall correctly, it also /can/ leave agent jobs hanging around on your production database if you select the 'schedule for later' option.
If you've got a handle on all that, then yes, it's simpler to use the copy database wizard, but not necessarily better.
You can script a prod to dev backup/restore/script logins/ routine that you run on prod, it takes a backup and outputs the commands to restore the backup along with the login scripting stuff.
You then run those output commands on the dev server. It works pretty well and if you develop it right is very re-useable too.
That's what I use because its fast and easy and 100% the same process every time.
~BOT
Craig Outcalt
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply