Litespeed for SQL Server Log shipping restore job is slow to complete. (4328009)

Litespeed for SQL Server Log shipping restore job is slow to complete.

Database fragmentation.

Please check and make sure that there is not Fragmentation within the transaction log being restored to the subscriber machine within your Litespeed Log Shipping as this has been known to cause the restore to run for longer periods than neccessary. 

ADDITIONAL INFORMATION:

For additional inof, see Kimberly Tripp's post:  http://www.sqlskills.com/blogs/kimberly/post/8-Steps-to-better-Transaction-Log-throughput.aspx

If you have a lot of autogrowth, you can later clean up the fragmentation that has occurred and get back to a reasonable, intact, and optimal transaction log. If you want to know more about Recovery Models and their impact on the transaction log, review a sample book chapter from an MSPress book (Microsoft® SQL Server™ 2000 High Availability). This chapter explains a lot about the general database environment settings that impact recovery. You can download Chapter 9: Database Environment Basics for Recovery here:http://www.sqlskills.com/resources/SQLServerHAChapter9.pdf

Read more: http://www.sqlskills.com/blogs/kimberly/post/8-Steps-to-better-Transaction-Log-throughput.aspx#ixzz19K8PuMWi

The Internal Notes for this solution exceeded the 2000 character size limit and have been saved in an external document that will be added as a non-Public Cloud attachment.