Log Reader hangs, runs for a day or more, or gives out of memory error
When using the Log Reader, one of the following scenarios happens and no transactions are returned.
1) Appears to hang. 2) Continues to run for a day or longer. 3) Returns an out of memory error.
T-log file is too large for the amount of resources (RAM, Free Space, etc.) available on the machine being used. Log Reader currently does not support a file with a large amount of data very well.
Use a top computer as a workstation, with more resources available, with very fast HDD and big RAM. It is recommended that free drive space be close to double whatever size the T-log is for best performance.
Waiting for enhancement request ID's 'TSS-639' and 'TSS-878' be implemented in a future release of Toad for SQL Server.
TSS-639 & TSS-878
Log Reader reads data from the server to the local computer to a temp file, parses it from Microsoft format, and then shows it in the UI.