InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 18 Jun 2013 22:45:16 GMT20http://www.sqlservercentral.com/Forums/Topic1406024-1549-1.aspxThanks for the response - confirms that we did not miss something obvious - checking the tables on the monitor server seems to be the best approach. We check SQL Agent from the file system already - easy enough to add log shipping monitor to the same routine.Tue, 22 Jan 2013 07:32:58 GMTbillh-508166http://www.sqlservercentral.com/Forums/Topic1406024-1549-1.aspxAll other ways will be just wastage if your sql agent services getting shutdown abruptly. Its good to find out reason for that and fixes that will be probably the best solution. Why don't you change the services parameter to start automatically when it stops. But still you can try the other way around:- Query the msdb.log_shipping_secondary_databases and related table from other server (May be Primary) using link server and send alert.RegardsDhananjayTue, 22 Jan 2013 03:56:11 GMTDhananjay-440114http://www.sqlservercentral.com/Forums/Topic1406024-1549-1.aspxYou can use the log shipping reports to monitor the state of the log shipping. These reports are standard. You can find more info on the link below:[url]http://msdn.microsoft.com/en-us/library/ms181149.aspx[/url]Sun, 20 Jan 2013 14:17:48 GMTIgnacio A. Salom Rangelhttp://www.sqlservercentral.com/Forums/Topic1406024-1549-1.aspxMonitoring Log ShippingMy client in Manhattan maintains a disaster recovery server in South Brooklyn. We employ log shipping to sync five databases. I have been trying to determine the best way to programmatically determine whether the databases are synchronized, or perhaps better, when they were last synchronized. The problem is complicated by the fact that the system appears healthy from the primary server’s perspective – it created the logs and shipped them successfully – but not from the secondary server’s perspective – sql agent shut down so logs were not restored and alerts not sent.Does anyone have suggestions regarding “best practices” to monitor system that employ’s log shipping. We do have a monitor server available, but it is currently on the same file system as the primary. I would rather not have to lobby for a third server – monitoring from the secondary would be fine if it can accurately tell me that status of the secondary in the event that the primary goes missing. Fri, 11 Jan 2013 07:30:41 GMTbillh-508166