May 13, 2009 at 8:18 am
We've set up log shipping from our on-line database to the standby server.
When we set up the first database for log shipping, the alert job for that database was properly created on the monitor server.
When we set up the second database for log shipping, the alert job for the second database was properly created on the monitor server. However, the first alert job has been deleted.
So, can a monitor server be used for monitoring multiple databases? BOL (http://msdn.microsoft.com/en-us/library/ms190224(SQL.90).aspx) doesn't mention whether one monitor server can monitor multiple databases.
Thanks,
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
May 13, 2009 at 8:32 am
If I am not mistaken, there is only one monitor job for all databases. This is differrent than the way it was in 2000. Let me see if I can find some documentation on it.
May 13, 2009 at 8:33 am
Here it is...
" A single monitor server can monitor multiple log shipping configurations. In such a case, all of the log shipping configurations that use that monitor server would share a single alert job."
http://msdn.microsoft.com/en-us/library/ms187103(SQL.90).aspx
May 13, 2009 at 8:53 am
Thanks Ken - I had the same question too. Your post confirmed my suspicion. But to me, this makes no sense. Log Shipping should set up an alert job for each Log Shipped database so that it allows you to manage them separately. For instance, if I want to see if my Log Shipping is in synch....don't I go to the Alert job and get status from there? Is there another way to see if LS is in synch. Also, if you want to disable log shipping jobs, you can't disable the Alert job, because it could be potentially Alerting for another database. Thirdly, if you want to just go and "View History" for that job, you can't see the history for each instance. It just makes no sense why they would set it up so that you can't have more than one Alert job on the monitor server. Any thoughts?
Dave Coats
May 13, 2009 at 10:57 am
Dave Coats (5/13/2009)
Thanks Ken - I had the same question too. Your post confirmed my suspicion. But to me, this makes no sense. Log Shipping should set up an alert job for each Log Shipped database so that it allows you to manage them separately. For instance, if I want to see if my Log Shipping is in synch....don't I go to the Alert job and get status from there? Is there another way to see if LS is in synch. Also, if you want to disable log shipping jobs, you can't disable the Alert job, because it could be potentially Alerting for another database. Thirdly, if you want to just go and "View History" for that job, you can't see the history for each instance. It just makes no sense why they would set it up so that you can't have more than one Alert job on the monitor server. Any thoughts?
Dave brings up some good points. If I fail over to my backup server, I would disable the existing log shipping jobs involved. As long as they are disabled, then this one alert job would constantly fail, even if it is monitoring other databases on other servers.
Ken, thanks for your reply.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply