November 24, 2010 at 12:26 am
Delete the entry from sysdatabase system table.
November 24, 2010 at 2:09 am
our db is still on recovery\read only mode, do you have query on that? or codes to execute this method you suggested: "delete entry from sysdatabase system table.
"
November 24, 2010 at 2:24 am
what do you get for your database when you run this:
select state_desc from sys.databases where name='test'
Online Trainer For SQL DBA and Developer @RedBushTechnologies with 18 yrs exp.
November 25, 2010 at 3:40 pm
Did you try starting SQL in Single-User mode with the No-Recovery Trace Flag, and then dropping the database?
Stop SQL Server and SQL Agent,
Add -m and -T3608 to the SQL Server Service startup parameters (use SQL Server Configuration Manager, in case you didnt know),
Start SQL Server, but NOT SQL Agent,
Log in and Drop the database (you may need to set to OFFLINE first, if not already done so),
Stop SQL,
Remove the -m and -T3608 startup parameters,
Restart SQL Server and SQL Agent.
November 25, 2010 at 8:01 pm
reshma_t22 (11/24/2010)
Delete the entry from sysdatabase system table.
First, direct manipulation of system tables is an extraordinarily BAD idea. Second, it's very difficult to do. I'm thinking that even you haven't ever done it before.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2010 at 8:03 pm
Build a new, empty database. Detach it and then try restoring that to the "bad entry". I've only had to do that once so I don't know if it'll work all the time but it's something else to try.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply