Timeline for Duplicate database and keep it up to date - Replication or SSIS?
Current License: CC BY-SA 3.0
4 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 10, 2011 at 13:47 | comment | added | Aaron Bertrand | You can log ship until you are ready to use the secondary as a staging database, then restore with recovery. When you're done using it, you can simply re-initialize log shipping. I've implemented fully-automated solutions exactly like this in the past. | |
Jun 10, 2011 at 6:44 | comment | added | Marian | @Aaron: I think I didn't read the last part of the question, about writing to this database :-). In this case the snapshot is, of course, invalid and I would go by your solution, backup and restore. Btw, how will log shipping help for this? In LS the databases are either in restoring mode or in standby, read-only... :-). | |
Jun 9, 2011 at 23:20 | comment | added | Aaron Bertrand | How can he use a database snapshot when the staging application needs to write to the copy without affecting the source? | |
May 5, 2011 at 7:20 | history | answered | Marian | CC BY-SA 3.0 |