sql server - sql transaction log backup theory -
the more transaction log more confused. think lot of people wrong. want make sure understand theory. please correct thinking if it's wrong.
the log has nothing full or diff backups (no tied or related in way). log contains changes database since last log backup. hence log chain. make changes database, copy placed in log , marked when it's committed database. think of full history of changes since beginning of time. gets cleared out when backup transaction log (log). continuous stream/record of changes.
yes, log chain starts first full backup ever created. fulls after don't reset log chain.
- load memory part of database going modified
- copy change/query transaction log
- make change loaded part in memory
- commit disk , checkpoints log
full-log-log-log-log
let's make full backup. log backups after. first log contain changes committed before full backup. it's nature of logs. again, logs aren't related in way full or diffs. assume when restore full logs after, know start restoring comparing date , time of full backup logs. don't want recommit changes done in full backup. thought process.
let's have backup process:
full weekly/diff nightly/logs hourly
for brevity's sake, won't fill example tons of log backups. should point across.
full-log-log-log-log-diff-log-log-log-log-diff-log-log-log-log
full-log-log-log-log-diff-log-log-log-log-diff-log-log-log-log
questions:
there seems 20 different answers online conflict each other. nobody can straight.
Comments
Post a Comment