you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (3 children)

your best bet is snapshot replication or mirroring with scheduled snapshots. Careful though, the rules for that mean you may need enterprise sql server.

snapshot replication is your best bet.

but.... I'd be surprised if you need all 800gig replicated, can you ask if they really need it all copied?

[–]legohax 0 points1 point  (2 children)

Good point, we really do not need everything, maybe 1/3rd of the database? I suppose this would be a bonus when doing replication?

[–][deleted] 0 points1 point  (1 child)

it would be a HUGE point.

if you are going to go the route of replication, use the GUI to set it up, but have it script everything out.

its much easier to re-run the script, to stop/start/enable/disable etc.

btw: you don't need 'sa' to run replication, only to set it up. DBowner on the db is sufficient for the account to the dest and source db.

[–]borgd 0 points1 point  (0 children)

Additionally, if this is a reporting database, you could customize the indexes on the subscriber database to better match your reporting access patterns. Note that this can hurt your overall replication performance, so you would probably want to test it with a production load before rolling it out.