Home Forums SQL Server 2008 SQL Server Newbies find out what transaction caused the log file to become full yesterday or day before yesterday RE: find out what transaction caused the log file to become full yesterday or day before yesterday

  • coolchaitu - Wednesday, December 6, 2017 12:32 PM

    Sue_H - Wednesday, December 6, 2017 10:54 AM

    coolchaitu - Wednesday, December 6, 2017 10:33 AM

    The error log has the following:
    SQL Server has encountered occurences of I/O requests taking longer than 15 seconds to complete on file g;|templog.ldf

    That's really a different error - could be indirectly related but it could just be from the file growing.
    You can see if or when a file grows in the default trace but it's not going to tell you what transaction.

    So for your first question, no.
    For the error you posted, take a look at this post to understand that error:
    Troubleshooting SQL Server I/O requests taking longer than 15 seconds – I/O stalls & Disk latency

    Sue

    I see that message before the tempdb log file full in error log

    So then you should read that article and follow the steps. There are other links in that article that you will want to check as well.

    Sue