PRB: sp_attach_db and CREATE DATABASE FOR ATTACH Do Not Remove Replication Tables (280295)


The information in this article applies to:

  • Microsoft SQL Server 7.0
  • Microsoft SQL Server 2000 (all editions)
This article was previously published under Q280295

SYMPTOMS

The sp_attach_db procedure and the CREATE DATABASE FOR ATTACH statement do not remove replication tables.

STATUS

This is behavior by design.

MORE INFORMATION

Only the sp_attach_single_file_db procedure removes the replication information from the attached database. If you use the CREATE DATABASE FOR ATTACH statement or the sp_attach_db stored procedure to create a new database, use sp_removedbreplication manually to remove the replication information.

If a database is being restored to the same server and database, replication is not removed. If the database is being restored to a different server or database, replication is removed.

It is possible to detach a transactional subscriber database. Detaching a SQL Server 7.0 database with transactional subscriptions and attaching it on SQL Server 2000 is not recommended. If this is required for some reason, you must run sp_vupgrade_subscriber_databases to upgrade the replication schema after attaching the database.
Modification Type:MajorLast Reviewed:10/16/2003
Keywords:kbprb KB280295
©2003 Microsoft Corporation. All rights reserved.