FIX: NO_TRUNCATE May Be Added to Backup Log Statement when You Perform a Log Backup from SEM
This article was previously published under Q285952
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 351714 (SHILOH_bugs)
By default, when you perform a transaction log backup from the SQL Server Enterprise Manager Backup Database dialog box, the Remove inactive entries from transaction log checkbox under the Options tab is selected so the backup should be performed without the NO_TRUNCATE option. However, if you perform the backup and you do not click the Options tab, the server issues the backup log statement with the NO_TRUNCATE option so the entries for completed transactions are not removed from the transaction log upon completion of the backup. If you click the Options tab before you perform the backup, the server issues the backup log statement without the NO_TRUNCATE option as expected.
To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
To work around this problem, use either of the following methods:
- Click the Options tab before you perform the backup and make sure that the Remove inactive entries from transaction log is selected.
- Issue the BACKUP LOG statement from the SQL Server Query Analyzer, and specify the exact options you need.
Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.
SEM SQL Enterprise Manager
Article ID: 285952 - Last Review: 01/16/2015 21:26:15 - Revision: 3.2
Microsoft SQL Server 2000 Standard Edition
- kbnosurvey kbarchive kbbug kbfix kbsqlserv2000sp1fix KB285952