Monitoring Log Shipped Databases
Posted
by Registered User
on Stack Overflow
See other posts from Stack Overflow
or by Registered User
Published on 2010-04-18T13:28:00Z
Indexed on
2010/04/18
13:33 UTC
Read the original article
Hit count: 190
log-shipping
|sql-server
I need a consistent way to monitor databases that are read-only log shipped copies of production databases. In the past I have relied on the following methods:
- Set the job that restores logs to the database kick off another job as its last step.
- Set the job that restores logs to the database to insert a record in a control table as its last step.
- Query the msdb database to check the status of the job that restores logs to the database.
- Query a control table inside the database itself that gets a value immediately before transaction logs are backed up.
- Query MAX values from tables inside the database to see if it has recent changes.
Although the above methods work, they can't be implemented for every log shipped database that I query for various reasons. What is the best method for monitoring the "data as of" date for a log shipped database?
© Stack Overflow or respective owner