This article was previously published under Q243377
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 56522 (SQLBUG_70)
When restoring the backup of a database, which is enabled for Transactional and Merge Replication (Sysdatabases.Category = 5), to a non-published database on a different server, the merge replication system tables are not dropped and the user tables on the destination server's database cannot be dropped. If the backup is restored on the same server (different database), then the restore works fine and the replication information is removed.
Also, the restore works fine across servers when the source database is enabled either for Transactional or Merge Replication only (Sysdatabases.Category = 1 OR 4).
To work around this problem, you can either:
Enable the source database for Transactional or Merge Replication alone (Sysdatabases.Category = 1 OR 4).
Drop the merge system tables using the DROP TABLE syntax.NOTE: Contact Microsoft Product Support Services if you need to drop the user tables and are unable to do so.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
Steps To Reproduce The Problem
Enable the database for both Transactional and Merge Replication (Sysdatabases.Category = 5).
The published database contains Conflict_<table_name> tables and MSmerge_% tables.
Backup the database.
Restore the backup to a database on a different server. The name of the database on the destination server does not matter.
RESULT: The replication information is not completely removed. The merge replication system tables are present. Following is a list of the tables that are present: