Override to not monitoring DB into SQL Server Instance
We have a SQL Instance with 10 DB. I've configured SCOM security on 9 DB. At this moment, I can't configure security on 1 DB (DatabaseA)
I've recieved alert on SCOM about this DatabaseA (Run As Account does not exist on the target system or does not have enough permissions). I've created a group with this database and I configure an override, but the alert appear again....
Alert: Management Group: xxxxxxx. Script: DiscoverSQL2008FileGroups.js : Cannot login to database [FQDN Instance][NetBios Instance:DatabaseA]
August 8th, 2012 1:20am
I've create override for:
1) This alert rule
2) Discover Databases for a database engine
3) Discover File Groups
But, I have the same problem. Alert always appear
Free Windows Admin Tool Kit Click here and download it now
August 8th, 2012 2:55am
Hi
For SQL 2008 - go to Authoring, Management Pack objects and Object discoveries.
- Scope for SQL Server 2008 DB and you'll see a discovery for "Discover databases for a database engine"
- Go to the overrides tab and choose override for specific object of class: SQL Server 2008 DB Engine and select the SQL Server instance
- You'll see an exclude list - "A comma-separated list of database instances that should be excluded from discovery. You can use the wildcard * to exclude all instances."
- Enter the database name for the database that you don't want to monitor
You might need to run a PSHell cmdlet (remove-disabledmonitoringobject) to actually clear it out of the database:
http://blogs.technet.com/b/jonathanalmquist/archive/2008/09/14/remove-disabledmonitoringobject.aspx
Cheers
Graham
Also see here -
http://social.technet.microsoft.com/Forums/en-US/operationsmanagermgmtpacks/thread/59f32d71-734f-48d1-b824-6da39a16c486/
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/
August 8th, 2012 4:08am