Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 Cannot remove replication
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Starting Member

4 Posts

Posted - 05/06/2006 :  18:15:28  Show Profile  Reply with Quote
Hi All,

I had a HDD failure that caused the database to become SUSPECT. Thats ok we have backups to fall back on. Restoring the database failed because the database is used for repliacation, the database status was set to LOADING (in middle of restore). Because of this status I am unable to remove the repliaction to allow the database restore.

Whats a way to change the database status from loading? Or is there any way of removing it completely and starting again from a backup? Can I force repliaction to be removed?

Thanks for taking the time to look at my problem, all help and suggestions are much appreciated.


Yak with Vast SQL Skills

899 Posts

Posted - 05/06/2006 :  18:27:47  Show Profile  Visit paulrandal's Homepage  Reply with Quote
Try the instructions here -

Paul Randal
Lead Program Manager, Microsoft SQL Server Storage Engine + SQL Express
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)
Go to Top of Page

Starting Member

4 Posts

Posted - 05/06/2006 :  18:57:44  Show Profile  Reply with Quote
Thanks for the advise, though I am not running SQL 2005(running SQL Server 2000 32-bit) and the stored procedure recommended in the linked artical - sp_removedbreplication does not have the @force parameter in versions before 2005.

Is there a way of getting the T-SQL for the new sp_removedbreplication? Or a different approach is needed?

Go to Top of Page


United Kingdom
12543 Posts

Posted - 05/06/2006 :  21:49:05  Show Profile  Visit nr's Homepage  Reply with Quote
Try restoring a small database over it.
There is something to do with replication that that resolves - not sure if it'sthis situation though.

Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

Starting Member

4 Posts

Posted - 05/07/2006 :  02:42:30  Show Profile  Reply with Quote
nr - your solution worked!! Don't know why but it did. Thanks nr and Paul for you help much appreciated

Go to Top of Page
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2019 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.03 seconds. Powered By: Snitz Forums 2000