Windows Server

gnat · Guest

Anyone know how to exclude a specific SQL2000 instance (not default) from
MOM2005? I know that you can identify a specific database for exclusion by
placing the SQLExclude.txt file on the C:\, but I am looking to prevent MOM
from monitoring a specific instance in it's entirety. The server has 2
instances installed (vendor screw up), and the least intrusive solution was
to just disable the services on the erroneous instance. Now that we are
implementing MOM, this instance get's picked up by the "SQL Server Service
Discovery" rule as an alert for having its services stopped.

Any advice would be greatly appreciated.

Justin Harter · Guest

I posted on many forums for this same question and found nothing. I don't
believe that there is an easy way to exclude an instance. I believe the only
way to get MOM to stop reporting on it is to remove the instance from SQL
completely.

gnat · Guest

Thanks for the reply.
I just wanted to see if I was missing something. We are pretty new to MOM
and are at the verge of committing to purchase and deployment. I reviewed
your recently posted and it looks like you have recently worked your way
through the steep learning curve. Thanks for all the helpful postings.

Have you run into any manger deployment issues with vendor or application
compatibility with the agent?

Have you discovered any surprises after you committed to deployment that
would have been good to know about in the early planning stages?

Thanks again,

	Windows Server Forum Index -> MOM	All times are GMT
Page 1 of 1