DBAmon dbc Configuration - MSSQL Parameters

DBAmon

dbc Configuration - MSSQL Parameters

MSSQL Parameters

Parameter Description Example Value Default Value

Backup_Age: (Optional) The maximum tolerable age of the most recent DB backup in hours. See below for details on which databases are checked. 32 (No Default)

Backup_Check_DBs: (Optional) The MSSQL databases that you want to preform Backup_Age: checking on. If you specify the Backup_Age: parameter, the master and msdb databases will automatically be checked. Specify here any additional databases for which you want to check backup age. The name must be specified in lower case and if there is more than 1 name, the names must be separated by commas with no spaces.
If you specify ALL, then all DB's will be checked for backup age.
northwind,mydb,yada,yada (No Default)

Backup_Command: (Optional) Specifies an NT command to invoke anytime a backup age event occurs for any database names in Backup_Check_DBs:. Note that you have to provide your own backup script which is invoked. You can specify predefined strings that will be translated at run-time:

{PERLPATH} - Translated to the ActivePerl Home Dir
{SQLPATH} - Translated to the MSSQL Home Dir
{DB} - Translated to the name of the DB that created this Backup Age event
DBAmon will choose the method for invoking this command based on the total size of all databases. If the size exceeds 200MB, the command will be invoked with the NT "start/b" command in the background. If the size is <= 200MB, then the command will be run in the foreground. When the command is invoked in the background, the output will not be logged (NT limitation). {PERLPATH}/perl.exe {SQLPATH}/scripts/backup.pl {DB} LVL0 (No Default)

Event_EMail_For_Sevs: (Optional) Normally DBAmon only sends an EMail notification for a Critical or User event. wWith this parameter you can specify additional event severities for which DBAmon SHOULD send EMail notification for events. PW
(This would add EMail notification for SEV=Performance and SEV=Warning events)

MSSQL_Agent_Mon: (Optional) If you do not wish to monitor to ensure that the MSSQL agent is running, specify N here. N Y

MSSQL_DB_OK_Owners: (Optional) DBAmon checks all Databases to ensure that they are owned by the SA userid. With this parameter you can specify additional userids which are allowed to own Databases. Multiple IDs can be specified but the y must be separated by a comma (no spaces). See the example to the right. theowner1,theowner2,me,you (No Default)

MSSQL_DDP_Job_Cat_MBR: <|> {JobCategory} <|> (Optional) Specify here the MSSQL JOB CATEGORY for job(s) that MUST BE RUNNING (get it? MBR=Must Be Running). Note that this parameter can be specified multiple time to specify multiple job categories that must be running. MSSQL_DDP_Job_Cat_MBR: <|>repl-distribution<|> (No Default)

MSSQL_DDP_Job_Name_MBR: <|> {JobCategory} <|> (Optional) Specify here the MSSQL JOB NAME for job(s) that MUST BE RUNNING (get it? MBR=Must Be Running). Note that this parameter can be specified multiple time to specify multiple job names that must be running. MSSQL_DDP_Job_Name_MBR: <|>The Job Name<|> (No Default)

MSSQL_Instance: (Optional) The name of this MSSQL instance. MSSQL1 MSSQLSERVER

MSSQL_Job_Fail_Check: (Optional) Specify Y or N to Enable or Disable SQL Job Failure checking. If the most recent job completion status for any enabled job is Failed, then this event will occur if this parameter is Y. Y (Depends on dbamonrc
Default_MSSQL_Job_Fail_Check: parameter)

MSSQL_Job_OK_Owners: (Optional) DBAmon checks all enabled SQL jobs to ensure that they are owned by the SA userid. With this parameter you can specify additional userids which are allowed to own jobs. Multiple IDs can be specified but the y must be separated by a comma (no spaces). See the example to the right. theowner1,theowner2,me,you (No Default)

MSSQL_Log_Min_Sev: (Optional) Use this parameter to optionally override the default value of 17. The value that you specify is the minimum SQL Log severity message that will become a critical event. For example, if you specify 14, then all SQL Log messages with a severity 14 or higher will be reported as critical events. 14 (Depends on dbamonrc
Default_MSSQL_Job_Fail_Check: parameter), or 17

MSSQL_String_Check: (Optional) Use this parameter to optionally search the SQL Log for strings that you want to keep track of. For example, if you want track deadlocks, you could specify a string that occurs in the SQL as part of the deadlock message. If the string is found, the PERFORMANCE VARIABLE that you name as the 2nd parameter (after the SLASH or /) is incremented for every match. You then can be notified when this occurs by specify the T_Perf_Counter: parameter. MSSQL_String_Check: recovery/String_Recovery
In this case, the string "recovery" will be searched for in the SQL Log.
If found, the DBAmon Performance Counter Variable
"SQL_UDM_String_Recovery" will be incremented.
(No Default)

NT_RCP_Bug: (Optional) We have found an NT bug where RCP from a Unix server (the DBAmon Master server) has a permission problem. Coding this parameter Y will cause a workaround to this problem to be used. If you get persistent \temp\dbamon* Permission Denied errors, then you may be experiencing this problem. Y (No Default)

Perl_Path: (Optional) If the ActivePerl executable is not in the default "Path", you will need to specify this parameter which needs to point to the actual ActivePerl executable. e:\perl\bin\perl (No Default - DBAmon will attempt to figure out the path for Perf by default)

SSH_Port: {PortNumber} (Optional) SSH communication to the TARGET defaults to using the SSH port of 22. If you need to use a different port, specify that port number here. Obviously, the port number that you specify here must match the port that you configured into your SSH Server Software(CopSSH). SSH_Port: 22222 22

T_* DBAmon Monitoring Threshold Parameters:
T_Disk_Full: ww/cc
-or-
T_Disk_Full: N (Optional) The warning (ww) and critical (cc) thresholds when checking the fullness of any Windows disk which contains at least 1 MSSQL database file. If you do not want this check to occur, specify N. 80/85 95/99

T_FG_Full: ww/cc
-or-
T_FG_Full: N (Optional) The warning (ww) and critical (cc) thresholds when checking the fullness of any SQL Filegroup. If you do not want this check to occur, specify N. 80/90 95/99

T_MSSQL_VLF_Count: nn (Optional) The Performance Event numeric threshold of the number of VLFs for the creation of a PERF event for this metric. 150 dbamonrc Default_T_MSSQL_VLF_Count value

T_PerfCounter: {PerfCounterName} W-Threshold/C-Threshold [Comparison-Operator] (Optional) This parameter is used to specify EVENT Warning and Critical thresholds for the Windows and MSSQL Performance Counters that DBAmon monitors. See the PERFORMANCE section of the INSTANCE DETAIL WWW page for the Performance Counter names. You must specify both a WARNING and CRITICAL threshold with the format: W/C. You can optionally specify a COMPARISON OPERATOR as the last parameter. It must be GT, GE, LT or LE. The default is GE (greater than or equal to). T_PerfCounter: SQL_ActiveTrans 10/15 GT (No Default)

T_TLog_Full: ww/cc
-or-
T_TLog_Full: N (Optional) The warning (ww) and critical (cc) thresholds when checking the transaction logs. If you do not want this check to occur, specify N. 80/85 95/99

MSSQL Parameters
Parameter	Description	Example Value	Default Value
Backup_Age:	(Optional) The maximum tolerable age of the most recent DB backup in hours. See below for details on which databases are checked.	32	(No Default)
Backup_Check_DBs:	(Optional) The MSSQL databases that you want to preform Backup_Age: checking on. If you specify the Backup_Age: parameter, the master and msdb databases will automatically be checked. Specify here any additional databases for which you want to check backup age. The name must be specified in lower case and if there is more than 1 name, the names must be separated by commas with no spaces. If you specify ALL, then all DB's will be checked for backup age.	northwind,mydb,yada,yada	(No Default)
Backup_Command:	(Optional) Specifies an NT command to invoke anytime a backup age event occurs for any database names in Backup_Check_DBs:. Note that you have to provide your own backup script which is invoked. You can specify predefined strings that will be translated at run-time: {PERLPATH} - Translated to the ActivePerl Home Dir {SQLPATH} - Translated to the MSSQL Home Dir {DB} - Translated to the name of the DB that created this Backup Age event DBAmon will choose the method for invoking this command based on the total size of all databases. If the size exceeds 200MB, the command will be invoked with the NT "start/b" command in the background. If the size is <= 200MB, then the command will be run in the foreground. When the command is invoked in the background, the output will not be logged (NT limitation).	{PERLPATH}/perl.exe {SQLPATH}/scripts/backup.pl {DB} LVL0	(No Default)
Event_EMail_For_Sevs:	(Optional) Normally DBAmon only sends an EMail notification for a Critical or User event. wWith this parameter you can specify additional event severities for which DBAmon SHOULD send EMail notification for events.	PW (This would add EMail notification for SEV=Performance and SEV=Warning events)
MSSQL_Agent_Mon:	(Optional) If you do not wish to monitor to ensure that the MSSQL agent is running, specify N here.	N	Y
MSSQL_DB_OK_Owners:	(Optional) DBAmon checks all Databases to ensure that they are owned by the SA userid. With this parameter you can specify additional userids which are allowed to own Databases. Multiple IDs can be specified but the y must be separated by a comma (no spaces). See the example to the right.	theowner1,theowner2,me,you	(No Default)
MSSQL_DDP_Job_Cat_MBR: <\|> {JobCategory} <\|>	(Optional) Specify here the MSSQL JOB CATEGORY for job(s) that MUST BE RUNNING (get it? MBR=Must Be Running). Note that this parameter can be specified multiple time to specify multiple job categories that must be running.	MSSQL_DDP_Job_Cat_MBR: <\|>repl-distribution<\|>	(No Default)
MSSQL_DDP_Job_Name_MBR: <\|> {JobCategory} <\|>	(Optional) Specify here the MSSQL JOB NAME for job(s) that MUST BE RUNNING (get it? MBR=Must Be Running). Note that this parameter can be specified multiple time to specify multiple job names that must be running.	MSSQL_DDP_Job_Name_MBR: <\|>The Job Name<\|>	(No Default)
MSSQL_Instance:	(Optional) The name of this MSSQL instance.	MSSQL1	MSSQLSERVER
MSSQL_Job_Fail_Check:	(Optional) Specify Y or N to Enable or Disable SQL Job Failure checking. If the most recent job completion status for any enabled job is Failed, then this event will occur if this parameter is Y.	Y	(Depends on dbamonrc Default_MSSQL_Job_Fail_Check: parameter)
MSSQL_Job_OK_Owners:	(Optional) DBAmon checks all enabled SQL jobs to ensure that they are owned by the SA userid. With this parameter you can specify additional userids which are allowed to own jobs. Multiple IDs can be specified but the y must be separated by a comma (no spaces). See the example to the right.	theowner1,theowner2,me,you	(No Default)
MSSQL_Log_Min_Sev:	(Optional) Use this parameter to optionally override the default value of 17. The value that you specify is the minimum SQL Log severity message that will become a critical event. For example, if you specify 14, then all SQL Log messages with a severity 14 or higher will be reported as critical events.	14	(Depends on dbamonrc Default_MSSQL_Job_Fail_Check: parameter), or 17
MSSQL_String_Check:	(Optional) Use this parameter to optionally search the SQL Log for strings that you want to keep track of. For example, if you want track deadlocks, you could specify a string that occurs in the SQL as part of the deadlock message. If the string is found, the PERFORMANCE VARIABLE that you name as the 2nd parameter (after the SLASH or /) is incremented for every match. You then can be notified when this occurs by specify the T_Perf_Counter: parameter.	MSSQL_String_Check: recovery/String_Recovery In this case, the string "recovery" will be searched for in the SQL Log. If found, the DBAmon Performance Counter Variable "SQL_UDM_String_Recovery" will be incremented.	(No Default)
NT_RCP_Bug:	(Optional) We have found an NT bug where RCP from a Unix server (the DBAmon Master server) has a permission problem. Coding this parameter Y will cause a workaround to this problem to be used. If you get persistent *\temp\dbamon Permission Denied** errors, then you may be experiencing this problem.	Y	(No Default)
Perl_Path:	(Optional) If the ActivePerl executable is not in the default "Path", you will need to specify this parameter which needs to point to the actual ActivePerl executable.	e:\perl\bin\perl	(No Default - DBAmon will attempt to figure out the path for Perf by default)
SSH_Port: {PortNumber}	(Optional) SSH communication to the TARGET defaults to using the SSH port of 22. If you need to use a different port, specify that port number here. Obviously, the port number that you specify here must match the port that you configured into your SSH Server Software(CopSSH).	SSH_Port: 22222	22
T_* DBAmon Monitoring Threshold Parameters:
T_Disk_Full: ww/cc -or- T_Disk_Full: N	(Optional) The warning (ww) and critical (cc) thresholds when checking the fullness of any Windows disk which contains at least 1 MSSQL database file. If you do not want this check to occur, specify N.	80/85	95/99
T_FG_Full: ww/cc -or- T_FG_Full: N	(Optional) The warning (ww) and critical (cc) thresholds when checking the fullness of any SQL Filegroup. If you do not want this check to occur, specify N.	80/90	95/99
T_MSSQL_VLF_Count: nn	(Optional) The Performance Event numeric threshold of the number of VLFs for the creation of a PERF event for this metric.	150	dbamonrc Default_T_MSSQL_VLF_Count value
T_PerfCounter: {PerfCounterName} W-Threshold/C-Threshold [Comparison-Operator]	(Optional) This parameter is used to specify EVENT Warning and Critical thresholds for the Windows and MSSQL Performance Counters that DBAmon monitors. See the PERFORMANCE section of the INSTANCE DETAIL WWW page for the Performance Counter names. You must specify both a WARNING and CRITICAL threshold with the format: W/C. You can optionally specify a COMPARISON OPERATOR as the last parameter. It must be GT, GE, LT or LE. The default is GE (greater than or equal to).	T_PerfCounter: SQL_ActiveTrans 10/15 GT	(No Default)
T_TLog_Full: ww/cc -or- T_TLog_Full: N	(Optional) The warning (ww) and critical (cc) thresholds when checking the transaction logs. If you do not want this check to occur, specify N.	80/85	95/99

DBAmon.com
This Document: http://www.dbamon.com/config/dbc_mssql.shtml