Timeline for Log Shipping vs Data Replication in SQL Server 2012
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:42 | history | edited | CommunityBot |
replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
|
|
| Feb 25, 2016 at 0:47 | vote | accept | user3015739 | ||
| Feb 25, 2016 at 0:46 | comment | added | user3015739 | I do not want to skip any logs but just in case, the SQL Server job failed due to some reasons, I can't proceed further. So, the only way I can resume the entire thing is to start from full backup. Correct ? | |
| Feb 25, 2016 at 0:21 | comment | added | Kin Shah | You cannot skip tlog .. it relies on log LSNs. Just make sure no one takes ad-hoc tlog backup. Copy only backup is fine. | |
| Feb 25, 2016 at 0:16 | comment | added | user3015739 | Thanks Kin. I will go for Log Shipping since I require the databases for archiving and reporting only. Got to research on the hardware requirement and support issues. Wonder how easy it is if we miss 1 transaction log. I guess, I can't proceed with the subsequent job if we miss one. Data will be out of synch. | |
| Feb 23, 2016 at 23:15 | history | answered | Kin Shah | CC BY-SA 3.0 |