May 22, 2013 at 4:00 pm
For you that use SCOM in your environment.
How do you treat the SQL management packs?
Do you let SCOM administrator just install the management pack and go with default options?
Do you still set up alerts or trust the management pack to raise the alarms?
Are you satisfied with SQL agent jobs just logging errors to eventlog where SCOM picks it up?
Do you sit down with SCOM administrator and configure alarms and thresh-holds? (if yes, maybe you have a link or list of suggestions)
Before I dive in to 90 pages of SCOM SQL management pack details, I would love to hear from you guys and how you treat SCOM vs SQL. Any best practise out there?
May 23, 2013 at 9:43 am
SCOM Admin deploys the management pack. We sit with them, go through the rules and monitors and agree whether they need to disabled or not. By default, most of the junk stuff will be enabled. Then we go through threshold values and stuff, like Wintel don't need to get alerted if CPU hits 90% threshold, instead, if it stays 90% for a period of time then it should or DBA team should get alert when the disk threshold reaches 80% etc etc.
May 24, 2013 at 3:25 am
Thanks for the input!
May 24, 2013 at 5:55 am
I have used (and managed) SCOM before. Now I am using RedGate Monitor. And let me tell you ... while less powerful and rich, I am extremely satisfied with RedGate. It is easier to configure, install and manage. I think for a small to medium company and for SQL alerts, it is a batter choice.
May 24, 2013 at 6:06 am
Thank's for the info.
SQL does not dictate if SCOM is used or not for my customers, I see the 3rd party tools as a compliment to SCOM and not as a replacement since
SCOM monitors all servers.
I would just like to utilize SCOM to its maximum for SQL, then I can have a look at other solutions as a compliment.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply