As you may know the DBCC CHECKDB process does not "error" if there are any issues with a database.
Yes this is not what one expects from an integrity test process but that is what we have to work with.
Yes I know there are many ways to skin a cat and this is a particularly tricky cat.
I have a SQL query that reads the log and determines if there are any issues (errors > 0)
The question is somewhat complex and that is why I am asking you experts in Solarwinds how best to go about raising the alert.
First my expectation:
Raise an alert when there are any issues with the DBCC CHECKDB process on any SQL Server in our environment. (about 100)
Method issues/options:
- Because SQL server does not raise an error the text values have to be examined on each server's error log to determine if there is an error.
(Read the log using SQL Query or SW Alert?) - Should the alert scan each server constantly or once per day after the DBCC checks have been completed ( various times around the clock)?
- Should I use SQL Scheduler to run the query and store the results in a table for Solarwinds to examine?
Suggestions please.
PS: is anyone has already solved this dilemma please speak up now!
All comments appreciated and suggestions investigated.
The reward at the end of this is a more reliable environment and less frazzled DBAs.
