Log Shipping conflicts

[RobertT687]

My company wants to use Log Shipping to maintain a backup database that will also serve as the reporting database. That is all queries should run against the backup server. We've tested the Log shipping procedures and they seem to be working OK for keeping the data in sync. One big problem we have seen in testing is when a log is being applied to the database and we try to run a query, the query fails because of locking during the log restore. Can anyone suggest a strategy to avoid the query failure? Queries can be run at anytime by the users and we don't want them to have to resubmit their queries because of the log restoration.

Thanks in advance for any help!!

 

[JayKusch]

If the users are expecting "near real time" reports, then you are stuck! When the log is being applied, there is no way of circumventing the locking issue. This is a needed occurence to keep integrity in check!

If the reports do not need to be real time, you could delay the LOAD of the shipped TLogs to maybe during a lunch time and then after-hours load. Or if they gen reports during the lunch time hour, delay the LOAD until after hours.


Thanks

J. Kusch