MSSQL SQL Log Message Exclusion

Home | Index/DBAmon Doc. | DBAmon Version/Change History | DBAmon Event/Error Doc. | What DBAmon Monitors | DBAmon Download | Free Oracle Tool: orastat | Request Support

MSSQL TLog Monitoring


By default DBAmon monitors the SQL Server "SQL Log" for any message with a severity of 17 or higher.

For example:

Error 50005, severity 19, state 1 was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage.  
In this case the error message number is 50005.

DBAmon excludes a few nuisance, non-actionable SQL messages number, such as 14151, 17806 and 18056. The exclusion is done by a file called dbamon_mssql.cfg which is downloaded from DBAmon to the TARGET server. One master copy of this file is pushed to all servers.

You may have a need for a unique copy of this file for a particular server with different message exclusion needs.

It is possible to create a LOCAL copy of this file which, if present, will be used INSTEAD of the master copy of the dbamon_mssql.cfg file which is pushed to all servers.

How It Works:

Note that the context of this document is a TARGET server running the "CopSSH" SSH Server software.

Follow these steps:

  1. In Windows Explorer, go to: C:\Program Files (X86)\ICW\home\dbmsmonitor (or whatever userid you are using).
  2. Copy the file dbamon_mssql.cfg to dbamon_mssql_local.cfg.
  3. Now make the changes to the CHKALERT E nnnnn lines to excluded the desired messages in the newly create file: dbamon_mssql_local.cfg.
Now, the DBAmon TARGET Probe will use this newly created file instead of the default file.
This Document: http://dbamon.com/config/mssql_message_exclude_override.shtml