August 21, 2002 03:21 PM

Log Backups Paused for Good Reason

Rating: (0)
SQL Server Magazine
InstantDoc ID #26032
Log backups are an important part of a full database backup. SQL Server backs up the transaction log as part of a full backup to make the full backup transactionally consistent when the full backup is restored. Before you can back it up, the transaction log needs to be accessible and complete: SQL Server must have access to all log activity that has occurred throughout the full backup, and the log can't have been cleared. However, the default transaction log backup behavior is to back up and then clear what was backed up. If log backups were allowed during a full backup, the full backup couldn't back up the log and thus would be transactionally consistent during a restore.

For...

...This article is for paid Professional Members only.

Already a Professional Member? Please log in now:

NOT A PROFESSIONAL MEMBER? YOU CHOOSE:

Professional Membership

Monthly

Annual

VIP Membership

Monthly

Annual

Add a Comment

How would this work for Yukon? Please let me know at arkhas@gmail.com

Anonymous User 11/16/2004 4:30:24 AM


I can't figure how to correct the situation

Microsoft OLE DB Provider for SQL Server error '80040e14'

The log file for database 'atrafdating' is full. Back up the transaction log for the database to free up some log space.

/left_frame_iframe.asp, line 42

Microsoft OLE DB Provider for SQL Server error '80040e14'

The log file for database 'atrafdating' is full. Back up the transaction log for the database to free up some log space.

/members_main.asp, line 97


Please answer to amuraim@yahoo.com

Amuraim Rotem 7/21/2003 11:48:15 AM


"(...)thus *WOULD* be transactionally consistent during a restore" (1st paragrph)

Isn't it *WOULDN'T* ?

Vinícius Oda 11/19/2002 8:22:34 AM


You must log on before posting a comment.

Are you a new visitor? Register Here
GOOGLE LINKS
SPONSORED LINKS
FEATURED LINKS