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

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 suspect database & full transaction log

Author  Topic 

brooksey
Starting Member

4 Posts

Posted - 2004-11-14 : 13:24:03
Hi,

I currently have a transaction log that is full, and I believe this is what has caused my database to become (suspect) I don't know what to do now. Because the Database is at suspect status I cant't truncate the transaction log.??????

Please Help......

nr
SQLTeam MVY

12543 Posts

Posted - 2004-11-14 : 13:46:26
see
http://www.nigelrivett.net/RecoverCorruptDatabase.html

==========================================
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

brooksey
Starting Member

4 Posts

Posted - 2004-11-14 : 13:52:29
To run the stored prcedures I need to be able to get into query analyzer, however it is not allowing me to do that.
Go to Top of Page

brooksey
Starting Member

4 Posts

Posted - 2004-11-14 : 14:11:26
OK....I have gone into Query analyzer and ran the sp_resetstatus and received the following

Prior to updating sysdatabases entry for database 'dynamicapp', mode = 0 and status = 4194320 (status suspect_bit = 0).
No row in sysdatabases was updated because mode and status are already correctly reset. No error and no changes made.


I have since then restarted SQL Server Service. But still sitting in suspect. Should I reboot the whole server? or proceed to emergency mode?



quote:
Originally posted by brooksey

To run the stored prcedures I need to be able to get into query analyzer, however it is not allowing me to do that.

Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2004-11-14 : 14:18:48
Setting it to emergency mode will allow you to access the objects in the databse and extract the data. You can always set the status back afterwards.



==========================================
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

brooksey
Starting Member

4 Posts

Posted - 2004-11-14 : 14:22:50
I am afraid, I am not sure what you are talking about here....my knowledge of SQL Server is poor. I do thank you for your help, I don't know if you would be willing to explain a little more in detail what you mean, but if you were willing I would be ever greatfull.

Karen


quote:
Originally posted by nr

Setting it to emergency mode will allow you to access the objects in the databse and extract the data. You can always set the status back afterwards.



==========================================
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

nr
SQLTeam MVY

12543 Posts

Posted - 2004-11-14 : 15:42:05
If you set the database to emergency mode then you can access the data. Enterprise manager probably won't be able to access it but query analyser and bcp will.
You can then extract all the data and import it into a new database.

Rather than this it would be better to restore the last backup but if that's not an option then this should allow you to recover most of the data.

==========================================
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
   

- Advertisement -