We have a SQL Server 7.0 database running with trunc. log on chkpt and
select into/bulkcopy checked and need to develop a backup strategy.
One of our DBAs insists that since the transaction log is being
truncated, we can't do a hot backup (a FULL backup in multiuser mode)
because if a transaction comes through during the backup it will leave
the backup in an inconsistent state. I'm skeptical, but I don't know
how SQL Server 7 avoids this problem.
If SQL 7 is not truncating the transaction log, it uses the
transaction log to roll forward changes that occurred during the
backup. Obviously if it's truncating the log it must have some way to
apply these transactions anyway (such as not doing a checkpoint during
the backup, backing up the log at each checkpoint, etc.).
Can anyone confirm that a hot backup will be valid when trunc. log on
chkpt is checked? Does anyone know how SQL 7 accomplishes this?
Thanks!
James