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 |
|
SamC
White Water Yakist
3467 Posts |
 Posted - 2004-07-12 : 11:35:11
|
| I use EM to make a local copy of a remote production DB occasionally.The remote DB is over 1GB now. Is there a better way to get a local copy ? Is it more efficent to restore a backup?Sam |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-07-12 : 12:22:51
|
| It's usually best to restore a backup. It tests your backup and has less impact on the network and source server (or it should).Also consider dmo for the copyseehttp://www.nigelrivett.net/SQL-DMOTransfer.html==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2004-07-12 : 14:04:23
|
| I normally don't need All Tables for this job, so I have a "PULL" script that pulls given tables into a TEMP database (SELECT * INTO LocalDB.dbo.MyTable SELECT * FROM RemoveDB.dbo.MyTable). No indexes etc. so generally quite small. Then I backup and pull that locally, restore and then PULL the tables back into the Real local database - which has indexes and all the other gear.It's all a bit of a palava, but worth it where I'm not interested in most of the data - like the voluminous log tables!Kristen |
|
|
|
|
|
|
Copy a DB