This procedure is meant to be run as part of a backup transaction job created as a component of a Database Maintenance Plan. It reads the most recent log file created by the maintenance plan and searches for a “nonlogged” error. This error occurs when a non-logged operation (such as a select into or a WRITETEXT that doesn’t specify WITH LOG) occurs. Rather than indicating a failure for a fairly common occurance, this procedure gets the name of the database and performs a differential backup to a file of the form:
Future transaction backups will then procede without error.
The best way to use this procedure is as “Step 2” of the backup transaction job created by the Database Maintenance Plan. Set the “Step 1” step to go to the next step if a failure occurs, and call this procedure as the next step.
Author: Vince Iacoboni
Disclaimer: We hope that the information on these script pages is
valuable to you. Your use of the information contained in these pages,
however, is at your sole risk. All information on these pages is provided
“as -is”, without any warranty, whether express or implied, of its accuracy,
completeness, or fitness for a particular purpose…
Back to Database Journal Home