Post reply

Database Suspect

  • December 2, 2003 at 3:26 pm

    #59509

    My test database went into Suspect status. So, per BOL, I ran sp_resetstatus and DBCC DBRECOVER and everything seemed OK. However, when I look into SQL Server Logs I see 'Starting database 'Test_Database' repeated over and over at least once per minute. Am unable to access Performance Monitor to see what is happenning on this server due to a stodgy Sys Admin.

  • December 3, 2003 at 12:55 am

    #484406

    Hi,

    I have never seen this before. Was there enough disk space for the Data files and Log files before running DBCC DBRECOVER.

    If it aint broke don't fix it!


    Andy.

  • December 3, 2003 at 9:43 am

    #484471

    Thanks for the note..... Space does not seem to be an issue (14 GB free). I'm left with the feeling that it's a memory problem and I can't check that as I don't have access to the server console. Will probably have someone over there look at the Performance Monitor.

  • December 4, 2003 at 7:24 am

    #484603

    sounds like you have the "auto close" database option set. With this option set, anytime the database is used, you will see this message in the SQL Server log.

  • December 4, 2003 at 9:39 am

    #484654

    Will check.... Is 'auto close' good or bad?

  • December 4, 2003 at 1:58 pm

    #484700

    You should read sp_dboption in BOL. I guess most folks here consider it bad.

    Frank

    http://www.insidesql.de

    http://www.familienzirkus.de

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • December 8, 2003 at 7:31 am

    #485082

    don't check "auto close" >>so make this check clear .. because it closes the DB

    also don't check "auto shrink" >>so make this check clear

    where these 2 check lead you into bad performance.

    Alamir Mohamed

    Alamir_mohamed@yahoo.com


    Alamir Mohamed
    Alamir_mohamed@yahoo.com

  • December 8, 2003 at 2:00 pm

    #485179

    You may also want to check the error logs. The last time I had a suspect database was after a server crash. There was a partial write causing a torn page in one database. All other databases on the server were fine. If you do have a torn page, unless you need specific time sensitive data, I would suggest a restore from your last known good backup. Good Luck.

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

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