Templog file grew to over 200 GB

  • I had a space issue on one of my SQL Server's because my templog file used all the avaliable free space. It had grown to over 200 GB under normal application conditions. Any idea why it would have grown that large?

    I stopped and restarted the SQL Server services to resolve the issue. Would there have been a better way to resolve this?

  • The thing you want to check is if there are open transactions in there. That is usually what causes the log to grow crazy. Or if youhave an extremely large load of some sort that used tempdb.

Viewing 2 posts - 1 through 1 (of 1 total)

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