Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > Configuration Wizard error: Cannot drop the table ‘dbo.Statusinfo’ because it is being used for replication

Configuration Wizard error: Cannot drop the table ‘dbo.Statusinfo’ because it is being used for replication

Created by Malik Haider, last modified by Malik Haider on Jul 02, 2017

Views: 305 Votes: 2 Revisions: 14

The database configuration fails while trying to restore a replicated database with the following error message:

Cannot drop the table ‘dbo.Statusinfo’ because it is being used for replication.

The same error message appears when running Configuration Wizard in an attempt to resolve the issue.

 

Tried to manually drop same Error " Cannot drop the table 'dbo.Statusinfo' because it is being used for replication  

 

You can also use the SQL Studio on the SQL sever directly and try to drop the table 

 

 

Environment

All NPM versions

Cause

Refer to SQL SERVER – FIX – ERROR : Cannot drop the database because it is being used for replication. (Microsoft SQL Server, Error: 3724) for the cause of this issue.

Is it recommended not to replicate any replication metadata tables. The Create Publication Wizard does not allow system tables to be replicated.  These same checks do not occur when you configure Replication using system stored procedures.

In the source database, if any of the replication system tables are marked for replication (like MSpeer_lsns..) using the stored procedures, restore of this database would fail with the above error message.

Resolution

Refer to Restore of Replicated Database fails with “Cannot drop the table <table name> because it is being used for replication.” to restore the database with KEEP_REPLICATION setting.

 

http://blogs.msdn.com/b/repltalk/arc...plication.aspx

  1. Restore the database with KEEP_REPLICATION setting.
  2. Drop all subscriptions using sp_dropsubscription
  3. Drop all the articles using sp_droparticle
  4. Remove replication using sp_removedbreplication stored procedure

Once Done . Re run the Configuration Wizard. 

Other Related article . 

http://blog.sqlauthority.com/2009/09...er-error-3724/

 

 

Last modified
05:34, 2 Jul 2017

Tags

Classifications

Public