Return
-
Title
Slow transaction log restore -
Description
When performing a t-log restore, with LogShipping on within a job, a restore may take a very long time to complete.
-
Cause
One possible cause could be the tlogs are badly fragmented.
Evidence of this would be the transaction logs have over 1000 VLFs.(Virtual log files)
For best performance it is recommended by Microsoft to not have more that 100 VLFs for one transaction log. -
Resolution
If the "status" field shows "0" for most if not all of the VLFs, customers should look into shrinking the transaction log to reduce the number of VLFs to less than 100.
This will increase perfomance of their tlog restores. (this link provides information on how to do this: http://www.sqlskills.com/BLOGS/KIMBERLY/post/8-Steps-to-better-Transaction-Log-throughput.aspx)