Post reply

Does a full Database log halt database operation?

  • April 11, 2005 at 1:39 pm

    #102476

    Does the following message halt database/Sql server operation?

    Critical Error - DB Name - Database log file is full. Back up the transaction log for the database to free up some log space.

     

     

  • April 11, 2005 at 1:46 pm

    #551950

    As far as I understand : if sql can't write to the log, it will not execute the statement. The word critical should also be self-describing.

  • April 11, 2005 at 3:51 pm

    #551976

    Following Remi's answer, the answer is definately yes it does halt database operation. The specified database will not be able to be modified if the log file is full. Other databases on the server will keep working though.

    --
    Chris Hedgate http://www.hedgate.net/
    Contributor to the Best of SQL Server Central volumes
    Articles: http://www.sqlservercentral.com/columnists/chedgate/

  • April 11, 2005 at 3:52 pm

    #551977

    thanks this is the answer i needed.

  • April 12, 2005 at 1:30 am

    #552044

    You should look into why you transaction log filled. What is your database recovery mode?. If it is full then you should be backing up the transactionlog regularly. If simple then make sure the log can autogrow enough.Also what operation where you doing to cause the log to fill (a large delete for example) - maybe the T-SQL needs to be examined.

Viewing 5 posts - 1 through 4 (of 4 total)

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