Copy Database
-
I have a need to duplicate our production database to a test server for developement. I can't decide which will be the best method to copy data-backup and restore to the test server, snap shot replication, or DTS copy DB job.
-
How often do you need to copy the data? Will the database on the test server be updated?
-
Agree - if 1 time | (or) occasional: bkup & Restore
If > 1|occasional: consider replication, DTS |log ship 😀
-
Chris Kempster did an article on this topic a while ago here.
Unfortunately with the Site Update I can't find it anymore. I'll keep digging and post when I've found it.
As has been it depends on how frequently you need this. For a once in a while action I'll prefer detaching, copying, attaching.
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url] -
In our environment which is multiple databases, multiple servers for Test/Dev/Prod I find it easier to do a backup and restore. We don't copy databases over on a routine basis it's just when it's required, which could be a few a day, a few a week or maybe a few a month - it depends on the current projects.
I've tried the copy database wizard and thought it was hopeless. I found it missed some objects like certain indexes and FK's.
I haven't tried replication or log shipping though. Our databases are pretty substantial, over 100 GB and I find it easiest to use SQL Litespeed to back up the DB and then copy the file to the new server and then restore with SQL Litespeed. The Litespeed backups aren't too big and with our Gigabit network between servers, it's a pretty quick process overall.
Cheers,
Angela
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply