Hi The SQL DB engine discovery is targetted at windows servers so you could: - create a group of windows servers (the one you don't want to monitor SQL on) - override the SQL 200x SQL DB Engine object discoveries - you'll need to do this for SQL 2000 \ 2005 \ 2008 - run the remove-disabledmonitoringobject PSHell cmdlet http://blogs.technet.com/b/jonathanalmquist/archive/2008/09/14/remove-disabledmonitoringobject.aspx http://technet.microsoft.com/en-us/library/gg132269.aspx Cheers GrahamView OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Graham, thanks for the quick reply. I done as you have said and it appears to be working, the SQL DB Engine entry for the server disappeared from the discovered inventory so I hope the alerts stop also. I will add some other servers in to the override group and hopefully they will remove and stop alerting also. If I've any problem I'll post back but so far so good! :-) Cheers

Hi Just be aware that you'll need to run the remove-disabledmonitoingobject cmdlet after adding a new bunch of servers to the group. You might want to do a quick check to make sure that the SQL databases and the SQL Agents \ SQL Agent jobs from these servers have been removed. They should go automatically with the parent object but they are distinct discoveries so it is worth a check to make sure they have gone. Cheers Graham View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Hi, we have OpsMgrR2 deployed in our enterprise. Our SQL admin has asked if I can stop ALL SQL alerts for a particular group of SQL servers (these are a mixture of SQL 2005/8 servers with multiple databases/instances running which are managed by external vendors rather than in-house and we have no management responsibility for) so our SQL admin doesn't need to know about them, though I still would like them monitored for general windows/Active directory health. I know I can create overrides for each alert as they appear in console, but this would be v time consuming with all the potential SQL alerts that could be generated. Another way I have though of was to try and follow the same principle which I have already implemented as per Kevins blog for undiscovery of SQLEXPRESS instances (http://blogs.technet.com/b/kevinholman/archive/2010/02/13/stop-monitoring-sql-express-and-windows-internal-database.aspx) but this undiscovers by instance not by server name. Ideally I would like to be able to create an override group and drop in the Windows computer names of the targets I want to stop SQL alerts for - then be able to select a high level SQL discovery to set enabled = false to 'undiscover' the list of servers no matter which version of SQL it is running or which databases etc it hosts and then hopefully ALL SQL alerts from the MP will be stopped. Can this be done - any help much appreciated... Cheers