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

    You need to look at more than just the last error / message before the error that got your attention. You need to look at several hours worth of log warnings and errors (and possibly informational messages) to understand everything the system was doing before the error. That will give you a clearer picture of what caused the problem.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.