Error 3724: Cannot Drop Database

Hello All,
I am trying to delete couple of database in SQL 2000, SP3 and getting this
error:
Error: 3724: Cannot drop database because it is being used for replication.
There are no publications or subscriptions for the databases either. I did
also run one remove publication procedure but that did not help either.
Is there anyway I can delete these databases? Will appreciate all help.
Thanks and Regards
--
Fakhruddin Zavery
Sr. Systems Analyst / Programmer
CATS Tanzania Ltd.
NIC Life House 4th Floor
P. O. Box 2569, Dar es Salaam, Tanzania
Tel. +255-22 2137915, 2112631
Fax +255-22 2113033, 2112916
Mob +255 744 277452
website: http://www.catsgroup.com
----
--
The Irony of Life is that, no one gets out of it Alive
----
--Heck... the easiest way is to just shut down SQL and rename the files. It will come up as suspect then you can delete them. Not the correct way though
Jeff|||I tried that as well Jeff, it came up as suspect but when I try to delete it
still gives me the same error.
I even tried issuing the command DROP database from master but the same
error coems up.
"Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> Heck... the easiest way is to just shut down SQL and rename the files.
It will come up as suspect then you can delete them. Not the correct way
though.
> Jeff|||Can't you just detach the database and delete the files?
"Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
news:uykRwvGKEHA.1392@.TK2MSFTNGP09.phx.gbl...
> I tried that as well Jeff, it came up as suspect but when I try to delete
it
> still gives me the same error.
> I even tried issuing the command DROP database from master but the same
> error coems up.
>
> "Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
> news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> > Heck... the easiest way is to just shut down SQL and rename the files.
> It will come up as suspect then you can delete them. Not the correct way
> though.
> >
> > Jeff
>|||If I try to detach it says cannot be detached because it is being used in
replication.
"Jo Segers" <segers_jo@.hotmail.com> wrote in message
news:#qaFC0GKEHA.3292@.TK2MSFTNGP11.phx.gbl...
> Can't you just detach the database and delete the files?
> "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
> news:uykRwvGKEHA.1392@.TK2MSFTNGP09.phx.gbl...
> > I tried that as well Jeff, it came up as suspect but when I try to
delete
> it
> > still gives me the same error.
> > I even tried issuing the command DROP database from master but the same
> > error coems up.
> >
> >
> >
> > "Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
> > news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> > > Heck... the easiest way is to just shut down SQL and rename the
files.
> > It will come up as suspect then you can delete them. Not the correct
way
> > though.
> > >
> > > Jeff
> >
> >
>|||Is it not possible to disable replication? (I don't use replication so I
have no experience with it.)
From the BOL:
To disable replication using the SQL Server Enterprise Manager
1.. Expand a server group, and then expand the Distributor (the server
that contains the distribution database).
2.. Right-click the Replication folder, and then click Disable Publishing.
3.. Complete the steps in the Disable Publishing and Distribution Wizard.
"Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
news:eulw24GKEHA.1388@.TK2MSFTNGP09.phx.gbl...
> If I try to detach it says cannot be detached because it is being used in
> replication.
> "Jo Segers" <segers_jo@.hotmail.com> wrote in message
> news:#qaFC0GKEHA.3292@.TK2MSFTNGP11.phx.gbl...
> > Can't you just detach the database and delete the files?
> >
> > "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
> > news:uykRwvGKEHA.1392@.TK2MSFTNGP09.phx.gbl...
> > > I tried that as well Jeff, it came up as suspect but when I try to
> delete
> > it
> > > still gives me the same error.
> > > I even tried issuing the command DROP database from master but the
same
> > > error coems up.
> > >
> > >
> > >
> > > "Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
> > > news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> > > > Heck... the easiest way is to just shut down SQL and rename the
> files.
> > > It will come up as suspect then you can delete them. Not the correct
> way
> > > though.
> > > >
> > > > Jeff
> > >
> > >
> >
> >
>|||If you post this in the replication group, I'm sure they will point you to the stored procedures you need to
call to make SQL Server forget about the replication.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> wrote in message
news:eulw24GKEHA.1388@.TK2MSFTNGP09.phx.gbl...
> If I try to detach it says cannot be detached because it is being used in
> replication.
> "Jo Segers" <segers_jo@.hotmail.com> wrote in message
> news:#qaFC0GKEHA.3292@.TK2MSFTNGP11.phx.gbl...
> > Can't you just detach the database and delete the files?
> >
> > "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
> > news:uykRwvGKEHA.1392@.TK2MSFTNGP09.phx.gbl...
> > > I tried that as well Jeff, it came up as suspect but when I try to
> delete
> > it
> > > still gives me the same error.
> > > I even tried issuing the command DROP database from master but the same
> > > error coems up.
> > >
> > >
> > >
> > > "Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
> > > news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> > > > Heck... the easiest way is to just shut down SQL and rename the
> files.
> > > It will come up as suspect then you can delete them. Not the correct
> way
> > > though.
> > > >
> > > > Jeff
> > >
> > >
> >
> >
>|||Jo been down that route as well but no luck, actually I had 3 databases to
delete all similar and perfoming same actions as this one, 2 of them I could
take them offline and delete after removing publications etc but this one I
can not delete for some funny reason.
"Jo Segers" <segers_jo@.hotmail.com> wrote in message
news:e716g#GKEHA.556@.tk2msftngp13.phx.gbl...
> Is it not possible to disable replication? (I don't use replication so I
> have no experience with it.)
> From the BOL:
> To disable replication using the SQL Server Enterprise Manager
> 1.. Expand a server group, and then expand the Distributor (the server
> that contains the distribution database).
>
> 2.. Right-click the Replication folder, and then click Disable
Publishing.
>
> 3.. Complete the steps in the Disable Publishing and Distribution
Wizard.
> "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
> news:eulw24GKEHA.1388@.TK2MSFTNGP09.phx.gbl...
> > If I try to detach it says cannot be detached because it is being used
in
> > replication.
> >
> > "Jo Segers" <segers_jo@.hotmail.com> wrote in message
> > news:#qaFC0GKEHA.3292@.TK2MSFTNGP11.phx.gbl...
> > > Can't you just detach the database and delete the files?
> > >
> > > "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
> > > news:uykRwvGKEHA.1392@.TK2MSFTNGP09.phx.gbl...
> > > > I tried that as well Jeff, it came up as suspect but when I try to
> > delete
> > > it
> > > > still gives me the same error.
> > > > I even tried issuing the command DROP database from master but the
> same
> > > > error coems up.
> > > >
> > > >
> > > >
> > > > "Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
> > > > news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> > > > > Heck... the easiest way is to just shut down SQL and rename the
> > files.
> > > > It will come up as suspect then you can delete them. Not the
correct
> > way
> > > > though.
> > > > >
> > > > > Jeff
> > > >
> > > >
> > >
> > >
> >
> >
>|||Thanks Tibor, will try and do that.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:#VwLgAHKEHA.2024@.TK2MSFTNGP11.phx.gbl...
> If you post this in the replication group, I'm sure they will point you to
the stored procedures you need to
> call to make SQL Server forget about the replication.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
>
> "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> wrote in message
> news:eulw24GKEHA.1388@.TK2MSFTNGP09.phx.gbl...
> > If I try to detach it says cannot be detached because it is being used
in
> > replication.
> >
> > "Jo Segers" <segers_jo@.hotmail.com> wrote in message
> > news:#qaFC0GKEHA.3292@.TK2MSFTNGP11.phx.gbl...
> > > Can't you just detach the database and delete the files?
> > >
> > > "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
> > > news:uykRwvGKEHA.1392@.TK2MSFTNGP09.phx.gbl...
> > > > I tried that as well Jeff, it came up as suspect but when I try to
> > delete
> > > it
> > > > still gives me the same error.
> > > > I even tried issuing the command DROP database from master but the
same
> > > > error coems up.
> > > >
> > > >
> > > >
> > > > "Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
> > > > news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> > > > > Heck... the easiest way is to just shut down SQL and rename the
> > files.
> > > > It will come up as suspect then you can delete them. Not the
correct
> > way
> > > > though.
> > > > >
> > > > > Jeff
> > > >
> > > >
> > >
> > >
> >
> >
>|||If you run:
sp_removedbreplication 'dbname'
go
exec sp_dboption 'dbname','published',false
go
exec sp_dboption 'dbname','merge publish',false
go
this should do it for you.
Regards,
Paul Ibison