First thing I turn off in EVERY environment is the SQL informational 
consistency check.  I have no clue why someone thought that was a good idea.

Used to be the disk fragmentation monitor, but we finally turned that off by 
default for 2012 disks... so I just have to disable it for 2008 and 2003.

Then We discuss whether they will consider the avg disk sec/transfer monitor, 
which tends to be noisy, as actionable.  If they don't, we disable it, if they 
do, we set it to an absurd number of consecutive samples to make it actionable.

Then I go configure their Healthservice restarts for HS and MH, per my blog.

I am sure many other consultants have their default stuff.


From: [email protected] [mailto:[email protected]] On 
Behalf Of Orlebeck, Geoffrey
Sent: Wednesday, February 24, 2016 8:53 AM
To: '[email protected]' <[email protected]>
Subject: [msmom] SQL DB Consistency Check:

All:

In almost every case, SCOM alerts to problems, not when something works 
correctly. However in the SQL MP there is a rule "Database consistency check 
performed with no errors" that generates an Information alert upon successful 
completion. From what I can tell this is merely checking for Event ID 8957 in 
the Application log on a server with a SQL DB Engine. Do you normally 
override/disable this monitor? Our SQL DBAs do their own health checks (which 
we haven't ingested into SCOM yet), including DB consistency so at this point I 
was going to disable the Rule. However, I wasn't sure if there is would be any 
issues I haven't accounted for in disabling it. Any opinions on whether the DB 
consistency check is worth keeping enabled?
Confidentiality Notice: This is a transmission from Community Hospital of the 
Monterey Peninsula. This message and any attached documents may be confidential 
and contain information protected by state and federal medical privacy 
statutes. They are intended only for the use of the addressee. If you are not 
the intended recipient, any disclosure, copying, or distribution of this 
information is strictly prohibited. If you received this transmission in error, 
please accept our apologies and notify the sender. Thank you.




Reply via email to