Post reply

MSDB in suspect mode

  • July 6, 2006 at 4:18 pm

    #168947

    My sql server 2000 msdb database is in suspect mode due to log space being maxed out.  I have tried just about everything which has not worked due to it being a system table, in suspect mode or not being in single user mode.

    I have been able to get it into emergency mode so i can read it and copy components to another database, but cannot recover this msdb database.  I do not have a backup (I know!, I Know!)

    Please let me know any additional steps i can take or maybe some detailed intsructions on single user mode.  I start the database in command line as single user, but when i launch the Sql Manager or Query Analyzer it get a message that the database is in single user mode and cannot log in at this time.

    Thanks

    Scott

  • July 10, 2006 at 8:00 am

    This was removed by the editor as SPAM

  • August 30, 2006 at 4:53 am

    #657454

    Try to disconnect your command line tool from database before you try to connect with QA.

    Then try

    sp_resetstatus [ @DBName = ] 'database'


    To learn is not to know.

  • November 9, 2007 at 8:36 pm

    #750029

    Hi,

    I think you will find the receipe in this link http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/06/619304.aspx

    Regards

    Ahmed

  • December 26, 2007 at 8:21 am

    #762680

    Can anyone guide me on how to get MSDB into emergency mode?

    Thanks,

    Jason

  • December 26, 2007 at 9:36 am

    #762706

    Did you try to read the page posted before your post? I mean http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/06/619304.aspx ... it is specified there how to put a database in "undocumented emergency mode".

    You can read http://www.spaceprogram.com/knowledge/sqlserver_recover_from_deleted_log.html too... I've used the technique described here once...

    Good luck, and read with more attention before posting.


    To learn is not to know.

  • March 13, 2008 at 12:23 am

    #788897

    try this one.....

    sp_configure 'allow update options',1

    reconfigure with override

    update the sysdatabases status column with the value -32768 for msdb database

    the msdb will go into emergency mode.

    Migrate the table data to from msdb database to another database with different name.

    now try to execute sp_resetstatus system procedure on the database msdb.

    rerun sp_configure 'allow update options',0

    reconfigure with override

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply