Mark, once a MS SQL transaction log sequence is started it is independent
of other backups, until the sequence is ended. SQL Server keeps track of
the logged transactions included in a backup. So, the first transaction log
backup after a full database backup will contain transactions from before,
during, and after the database backup. But no transaction that is already
part of the database backup will be duplicated when the database and log
backups are restored.

Because the database and log backup sequences are independent, restoring
any database backup and all of the transaction log backups since that
database backup is functionally the same as restoring the latest database
backup and all of the logs since it.

A full database backup does not backup the entire transaction log; it backs
up only the part of the transaction log that contains the transactions that
occurred during the database backup. And it does that to ensure it can
restore the database to a consistent state as of the end of the database
backup.

Bob King    IBM Global Services    Tivoli Data Protection Product Transfer
607-752-2074  (tie 852-)      bobking AT us.ibm DOT com


Mark D Baker <mbake5 AT JCPENNEY DOT COM>@VM.MARIST.EDU> on 04/19/2001 03:06:36 
PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  SQL Agent



I noticed that the complete database backup does not truncate the log
afterwards.  Will the first transaction log backup after the
complete database backup contain transactions from both before and after
the complete database backup?  If so, will applying the transaction log
backup to the restored database duplicate the transactions created
before the complete database backup?  Thanks.