enterprise manager loading DB

Hello
I have a problem with a loading DB in Enterprise Manager.
I had restored a DB from another Sql Server and something seems wrong. Ive
got no error message but I have a grey DB Icon with my DB Name and a loading
behind the name. I cant delete the DB with Enterprise manager, cant open
the properties nothing.
I have tried in Sql Query analyzer to drop the database, but Ive got an
error that the db cant be deleted because an use for replication exist.
On the Sql Server where I have restored the DB is no replication configured
only on the sql server where the backup was made.
Any idea how to remove the DB?
(Sql Server 2000 sp3)
Thx
BjrnPerhaps the restore was done using NORECOVERY option? Try:
RESTORE DATABASE dbname WITH RECOVERY
That would make the database accessible. Then drop the database, possibly re
moving replication
config first if needed (Google for details...).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bjrn" <prodevelop@.gmx.net> wrote in message news:O0SgxiqyGHA.3568@.TK2MSFTNGP03.phx.gbl...[
vbcol=seagreen]
> Hello
> I have a problem with a loading DB in Enterprise Manager.
> I had restored a DB from another Sql Server and something seems wrong. Iv
e
> got no error message but I have a grey DB Icon with my DB Name and a loadi
ng
> behind the name. I cant delete the DB with Enterprise manager, cant open
> the properties nothing.
> I have tried in Sql Query analyzer to drop the database, but Ive got an
> error that the db cant be deleted because an use for replication exist.
> On the Sql Server where I have restored the DB is no replication configure
d
> only on the sql server where the backup was made.
> Any idea how to remove the DB?
> (Sql Server 2000 sp3)
> Thx
> Bjrn
>[/vbcol]|||Hi,
Add on to Tibor; You could also try
RESTORE LOG dbname WITH RECOVERY
Thanks
Hari
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:ehrzeNsyGHA.4976@.TK2MSFTNGP04.phx.gbl...
> Perhaps the restore was done using NORECOVERY option? Try:
> RESTORE DATABASE dbname WITH RECOVERY
> That would make the database accessible. Then drop the database, possibly
> removing replication config first if needed (Google for details...).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Bjrn" <prodevelop@.gmx.net> wrote in message
> news:O0SgxiqyGHA.3568@.TK2MSFTNGP03.phx.gbl...
>|||Hi
Thx for your answer
Now the DB is deleted
regards
Bjrn
"Hari Prasad" <hari_prasad_k@.hotmail.com> schrieb im Newsbeitrag
news:#tECW2wyGHA.3568@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Add on to Tibor; You could also try
> RESTORE LOG dbname WITH RECOVERY
> Thanks
> Hari
> SQL Server MVP
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in
> message news:ehrzeNsyGHA.4976@.TK2MSFTNGP04.phx.gbl...
possibly[vbcol=seagreen]
an[vbcol=seagreen]
exist.[vbcol=seagreen]
>