November 11, 2011 at 2:23 pm
Is there any way to gather additional mirroring logging beyond the standard SQL error log?
Also, we randomly get alerts like these throughout the day:
"Unrestored log threshold"
"The mirroring connection to "TCP:..." has timed out for database "LogDB" after 10 seconds without a response.
Whenever we encounter these I check the mirroring configuration and everything is up and running as expected. Are these caused by random network hiccups? Are these types of errors normal and expected? Should they be ignored?
BTW, this is SQL2K8 R2 with a seperate primary, mirror and witness.
November 12, 2011 at 5:13 am
Is there any way to gather additional mirroring logging beyond the standard SQL error log?
In addition to using the Database Mirroring Monitor and dbmmonitor stored procedures to monitor a mirrored database and set up alerts on monitored performance variables, Microsoft SQL Server 2008 provides the following:
•Database mirroring metadata in catalog views.
•Performance counters for database mirroring
•Database mirroring event notifications
•Server events for the WMI Provider for Server Events.
Additional Sources of Information about a Mirrored Database
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply