Transaction log reader issue

Toad for SQL Server
1

we can read transaction log small size successfully but failed to read transaction log big size 337 M .

Is there anyone face this issue before ?

Thanks

2

Yes, this can happen.

When Toad for SQL Server reads SQL Server transaction logs, performance and success depend heavily on:

  • log file size

  • VLF (Virtual Log File) structure

  • amount of active log records

  • SQL Server load during read

  • time range being scanned

A 337 MB log is not inherently large, so the issue is usually not size itself, but one of the following:

  • Too many VLFs (very common)

    If the log was grown in small increments, it may contain hundreds or thousands of VLFs.
    Result: log reading becomes extremely slow or fails.
    You can check with: DBCC LOGINFO

  • If the log contains a lot of active transactions or high write activity:

    • reading may time out
    • log scan cannot complete efficiently

What to try

  • Check VLF count (DBCC LOGINFO)
  • Try reading during low activity period
  • Ensure latest Toad for SQL Server release is used
  • Compare behavior with SSMS function fn_dblog (if accessible)

If the issue persist, open a support ticket at support.quest.com for more support/dev help on this.