Replication or Log Shipping come to mind. Log Shipping is probably the simplest.

You could export/import the data, but that might be cumbersome and take a while.

Thanks, I might revisit when I get more space.

As to the OP, my strategy isn't any different for a big db than it is for a small one. Make sure...

We're on RG 6.0 now, so I think it was 5.0 at the time (about a year ago). I couldn't determine if it was related to the large amount...

jodieevans (5/14/2010)

---

Thanks for your help so far.

I chose snapshot replication because our reporting database needs to be a snapshot of out live database taken at the start of each working...

I have a 1.2 T database. We use BackupExec straight to tape because we don't have space to hold a native backup on disk. We tried using Redgate, but it...

If you create a new backup device, do you get the same result ?

Greg Charles (5/26/2010)

---

This will create a new table and populate it with the result set of the select from source table. ...

I don't know what the problem is. I just created a Backup Device and gave it a name and destination path. Then, after creation, look at properties & on General...

Are the live backup jobs referencing that backup device ?

passivebyz (5/26/2010)

---

Thanks,

I'm looking for a script which will include the logic to send an email when blocking occurs that includes the information such as what sessions were blocked and what...

In what way is it not working correctly ?

Maybe the network admin has setup BackupExec jobs backing up databases directly to tape.

You could add [font="Courier New"]bs.user_name [/font]to your query and see what it shows for those entries.

The best precaution is a full backup.

I can't see how detach-attach would have any effect on the database. There must have been some other action that occured either before or after.

Edited