Loading Databases SQL 7.0

  • When a database is 'stuck' in 'Loading' Mode is there a quick and safe way to stop and start the database successfully?

  • Define what you mean by 'stuck'.

    Generally most quick ways aren't really safe. You could try restarting the MSSQLServer service. I've found in the past that SQL generally recovers pretty well after a restart.

    Hope this helps

    Phill Carter

    --------------------

    Colt 45 - the original point and click interface

    --------------------
    Colt 45 - the original point and click interface

  • quote:


    Define what you mean by 'stuck'.

    Generally most quick ways aren't really safe. You could try restarting the MSSQLServer service. I've found in the past that SQL generally recovers pretty well after a restart.

    Hope this helps

    Phill Carter

    --------------------

    Colt 45 - the original point and click interface


  • Phil,

    The Database was in 'loading' mode, looking via Enterprise Manager, and wasn't changing its status for over an hour!

  • Have you tried detaching the database and then attaching it again.

    Pay Respect to People on your way up. For you will meet the same People on your way down.


    He who knows others is learned but the wise one is one who knows himself.

  • quote:


    The Database was in 'loading' mode, looking via Enterprise Manager, and wasn't changing its status for over an hour!


    Depending on the size of the database, it could take that amount of time, or even longer, for SQL Server to do it's recovery. Are there any messages in the Error log? You'll need to find out what the id number is for the database. Check sysdatabases in the master database.

    Hope this helps

    Phill Carter

    --------------------

    Colt 45 - the original point and click interface

    --------------------
    Colt 45 - the original point and click interface

  • Any clues to what the database is doing in the SQL log file?

    Regards

  • Have you recently restored this database? The loading state usually means that the database is waiting for more restores to happen e.g. transaction logs to be applied. It prevents people accessing the db in the middle of these restores.

    From query analyzer

    restore database yourdbname with recovery

    should get you back and running

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

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