Log file autogrow occurred on database

  • What does this mean 'Log file autogrow occurred on database'?

    When I check available free space it is 0% for log file.

    What is the recommendation?

  • Additional Information, log file have fixed size to grow e.g :10 GB

  • Fixed it, log backup was not taken before.

  • Any database with the recovery model set to Full will require log backups. If the log isn't backed up and autogrowth is enabled, you'll see auto grow occurring. Normal operations.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • Log files must be sequentially written. The spid that grows the log file by 10GB will have exclusive access, until 10GB is written. Other spids must wait. If SQL Server's clients use a 30 second timeout setting and also need to write to that log file, they will wait the additional time needed for that 10GB growth and might raise their timeout. Consider a lower growth setting. I use 250MB, and I invariably do not shrink my log file.

  • This was removed by the editor as SPAM

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

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