FIX: SQLDMO Transfer Operation Truncates Transaction Log of Destination Database (316213)

SYMPTOMS

You use the SQL Distributed Management Objects (SQL-DMO) Transfer object to move objects from one SQL Server database to another SQL Server database. When you move the objects into the destination database, the following query may execute multiple times in the destination database:

dump tran [<destination database name>] with no_log

The query disables the transaction restore from the point of the transfer until you perform either a full database backup, a differential database backup, or a filegroup backup. The Data Transformation Services (DTS) Copy SQL Server Objects task uses the SQL-DMO Transfer Object to move data and hence causes the same problem.

NOTE: If this occurs in a Log Shipping source database, it stops the Log Shipping process.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How To Obtain the Latest SQL Server 2000 Service Pack

WORKAROUND

To work around this problem, you can use any of the following import or data migration capabilities on a recurring basis without truncating the transaction log:

SQL Server Replication
Bcp.exe utility
Transact-SQL BULK INSERT command
SQL-DMO BulkCopy object
Data Transformation Services (DTS) Bulk Insert task
Data Transformation Services (DTS) Transform Data task

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.

MORE INFORMATION

This is not an issue with versions of SQL Server prior to SQL Server 2000, because the bulk import or data migration operations prevent the ability to perform a transaction restore until you perform a database backup.