February 12, 2006 at 3:39 am
Some DBAs recommend that you backup the T-Log after a full database backup. However, I don't understand why that may be necessary since the full database backup captures all the transactions that take place from the start of the backup through the point when all extents have been captured by the full database backup by appending the T-Log between those two points to the backup. Am I missing some point? Please clarify.
Also, is it possible to perform a bulk load while performing a full database backup or t-log backup? If it is, let's suppose that the database is running in bulk-logged mode, and you do a full database backup while you perform a bulk load. Will SQL Server capture all the BCM pages that changed as a result of the bulk operation and append it to the database backup if the bulk load was committed before the backup ended?
February 13, 2006 at 4:07 am
=======
Some DBAs recommend that you backup the T-Log after a full database backup. However, I don't understand why that may be necessary since the full database backup captures all the transactions that take place from the start of the backup through the point when all extents have been captured by the full database backup by appending the T-Log between those two points to the backup. Am I missing some point? Please clarify.
=========
It doesnot make any sense to take T-Log backup after full backup. Any DBA on this forum who said this?
February 13, 2006 at 4:36 am
I don't remember the DBA who quoted this but he did make a statement regarding taking a log backup after a full database backup. But thanks for your response anyway.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply