IBM Tivoli Composite Application Manager for Microsoft Applications, Version 6.3.1

Configuration settings

You can specify the SQL Server agent configuration settings in the interfaces that include the Manage Tivoli Enterprise Services window, the Tivoli Enterprise Portal, and the tacmd command line.

Table 1 contains a list of the configuration settings for each of the interfaces where you can specify these settings and a description of each setting.

Table 1. Names and descriptions of configuration settings for each interface
Interfaces where configuration settings are specified			Description	Examples
Manage Tivoli Enterprise Monitoring Services window	Tivoli Enterprise Portal	tacmd command line	Description	Examples
Server Name	Database Server Instance Name¹	`INSTANCE=InstanceName`	Name of the SQL Server instance that is to be monitored. Use MSSQLSERVER as the instance name for the default instance. The name must be short enough to fit within the total managed system name, which must be between 2 and 32 characters in length.	If the SQL Server instance being monitored is the default SQL Server instance, enter `MSSQLSERVER` in this field. If the SQL Server instance being monitored is a named instance with the instance name of `mysqlserver` and the host name is `popcorn`, enter `mysqlserver` in this field.
Login	Database Server User Id¹	`DBSETTINGS.db_login =UserId`	SQL Server user ID to be used to connect to the SQL Server. See Permissions required for configuring the monitoring agent for more information. Login is required only when `Windows Authentication` parameter is set to `False`. Use only ASCII characters.
Password	Password¹	`DBSETTINGS.db _password=Password`	Password for the SQL Server user ID. Password is required only when `Windows Authentication` parameter is set to `False`. Use only ASCII characters. Important: A password cannot be blank. If you specify a login name, you must enter a password.
Database Version	The version of the SQL Server instance.	This parameter need not be specified in the tacmd command.	The database versions for the SQL Server.	The database versions for the SQL Server instance are as follows: Microsoft SQL Server 2016 - 13.0.1601.5 Microsoft SQL Server 2014 - 12.0.2000.8 Microsoft SQL Server 2012 - 11.0.2100.60 Microsoft SQL Server 2008 R2 - 10.50.1600.1 Microsoft SQL Server 2008 - 10.0.1600.22
Home Directory	Database Server Home Directory Path¹	`DBSETTINGS.db _home=HomeDirPath`	Install directory Server instance monitored.	The default home directory path for the default SQL Server 2005 instance is C:\Program Files\Microsoft SQL Server\MSSQL. A named SQL Server 2005 instance has a default home directory path in the format `C:\Program Files\Microsoft SQL Server\MSSQL$instance_name`, where `instance_name` is the SQL Server instance name.
Error Log File	Database Server Error Log File¹	`DBSETTINGS.db _errorlog=ErrorlogPath`	Fully qualified location and name of the SQL Server Error Log	The default error log path for the default SQL Server 2005 instance is C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG. A named SQL Server 2005 instance has a default error log path in the format `C:\Program Files\Microsoft SQL Server\MSSQL$instance_name\LOG\ERRORLOG`, where `instance_name` is the SQL Server instance name.
Windows Authentic- ation	Windows Authentic- ation	`DBSETTINGS.db _winauth= 1/0`	Enables or disables Windows Authentication If the Windows Authentication check box is selected, windows credentials will be used for authentication. Remember: If you do not select the Windows Authentication check box, you must specify values for the Login and Password parameters. If you do not specify these parameters and click OK in the Database Server Properties window, an error message is displayed in a pop-up window and the agent configuration does not finish.	DBSETTINGS.db_winauth=1 —OR— DBSETTINGS.db_winauth=0
Support Long Lived Database Connections	Support Long Lived Database Connections	`DBSETTINGS.db _lldbconn= 1/0`	Enables or disables long lived database connections The following Take Action commands do not use Long Lived Database Connections: Database Check-up and Tune-up Dump Database Dump Transaction Log Rebuild Fragmented Indexes Refresh Query Optimizer Statistics Update Space Usage Information The following attribute groups do not use Long Lived Database Connections: MS SQL Text MS SQL Filegroup Detail MS SQL Server Summary	DBSETTINGS.db_lldbconn=1 —OR— DBSETTINGS.db_lldbconn=0
Extended Parms	Extended Parms	`DBSETTINGS.db _extparms="KOQTBLD"`	Disables capture of Table Detail attributes.	To disable the data collection for the Table Details attribute group, enter `koqtbld` in the Extended Parms field. Remember: To disable data collection for the Table Detail and Database Detail attribute groups, type `koqtbld,koqdbd` in the Extended Parms field.
Extended Parms	Extended Parms	`DBSETTINGS.db _extparms="KOQDBD"`	Disables capture of Database Detail attributes.	To disable the data collection for the Table Details attribute group, enter `koqtbld,koqdbd` in the Extended Parms field. Remember: To disable data collection for the Table Detail and Database Detail attribute groups, type `koqtbld,koqdbd` in the Extended Parms field.
Database	Include or Exclude Database name(s)	`DBSETTINGS.db_include_state=x`	To select the databases for monitoring, specify a value for this parameter. To monitor particular databases, select Include from the list, and then specify the names of the databases in the text field next to the list. To exclude particular databases from being monitored, select Exclude from the list, and then specify the names of the databases in the text field next to the list. Note: To enable or disable the monitoring of particular databases, clear the Monitor All Databases check box.	While configuring the agent remotely, use one of the following values in the DBSETTINGS.db_include_state=`x` command: If the value of `x` is 0, the database names that are specified in the text field are monitored. If the value of `x` is 1, the database names that are specified in the text field are excluded from being monitored.
Database (Continued)	Monitor all databases	`DBSETTINGS.db_monitorall_state=x`	To monitor all the databases of an SQL server instance, ensure that the Monitor All Databases check box in the Databases group area is selected. If you clear the Monitor All Databases check box, then you must specify the list of databases for which you want to enable or disable monitoring, in the text field under the Databases group area. If you do not specify the databases to be monitored, an error message is displayed in a pop-up window when you click OK, and the agent configuration fails.	In the DBSETTINGS.db_monitorall_state=`x` command, specify one of these values when you configure the agent: The value 0 for `x` indicates that the database names in the text field are monitored. The value 1 for `x` indicates that all the databases are monitored.
Database (Continued)			Remember: If you select the Monitor All Databases check box and also specify the databases to monitor in the text field under the Databases group area, then priority is given to the value of the Monitor All Databases check box. The list of databases that you specify in the text field is ignored.
Database (Continued)	Database list to include or exclude	`DBSETTINGS.db_list`	Use the text field to filter databases that you want to monitor. To specify database filter, you must first select a separator. A separator is a character that distinguishes a database name or database expression from the other database name or database expression. While selecting a separator, ensure that database names and database expression do not contain the character that you choose as a separator. You must not use the wildcard characters that are typically used in the T-SQL query (for example, %, _, [ ], ^, -) if they are used in the database names or database expression.	Examples of filters: Case 1: `% usage` Example: `@@%m%` Output: All the databases that have the character m in their names are filtered. Case 2: `_ usage` Example: `@@____` Output: All the databases that are of length four characters are filtered. Case 3: `[] usage` Example: `@@[m]___` Output: All the databases of length four characters and whose names start with the character m are filtered. Case 4: `[^] usage` Example: `@@[^m]%` Output: All the databases (of any length) except those whose names start with the character m are filtered.
Database (Continued)			When specifying database filter: Database names must start with a separator. Database expression must start with two separators. Note: Database expression is a valid expression that can be used in the `LIKE` part of the `T-SQL` query. However, you cannot use the `T-SQL ESCAPE` clause while specifying the database expression. The following workspaces are affected by database filter: Database Information Enterprise Database Summary Device Detail Table Detail Filegroup Detail	Case 5: Wrong input Example: `@%m%` Output: None of the databases are filtered. Case 6: Default Example: Field left blank (No query is typed) Output: All the databases are filtered. Case 7: Mixed patterns Example: `@@[m-t]_d%` Output: All the databases (of any length) whose names start with the characters m, n, o, p, q, r, s, t, followed by any character, with the character d in the third place are filtered.
Day(s) Frequency	Table Detail Collection Day(s) Frequency³	`DBSETTINGS.db_tbld _daily`	Use this feature to define the frequency of collecting data of Table Detail attributes. The values can be from zero to `31`.	DBSETTINGS.db_tbld_daily=1
Weekly Frequency	Table Detail Collection Weekly Frequency³	`DBSETTINGS.db_tbld _weekly`	Use this feature to specify a particular day for collecting data for Table Detail attributes. The values can be from zero to seven.	DBSETTINGS.db_tbld_weekly=1
Monthly Frequency	Table Detail Collection Monthly Frequency³	`DBSETTINGS.db_tbld _monthly`	Use this feature to define the data collection of Table Detail attributes on a particular day of the month. The possible values are `1`, `2`, `3`, and so on.	DBSETTINGS.db_tbld_monthly=5
Collection Start Time	Collection Start Time Hour	`DBSETTINGS.db_tbld _coll_stime_hour`	The possible values are zero to `23`. The default value is zero.	DBSETTINGS.db _tbld_coll_stime_hour=1
Collection Start Time	Collection Start Time Minute	`DBSETTINGS.db_tbld _coll_stime_minute`	The possible values are from zero to `59`. The default value is zero.	DBSETTINGS.db _tbld_coll_stime_minute=59
Table Detail Continuous Collection	Table Detail Continuous Collection	`DBSETTINGS.db_tbldconcoll`	Use this feature for the continuous background collection of Table Detail data. The Table Detail Continuous Collectioncheck box is selected by default.	DBSETTINGS.db_tbldconcoll=1
Interval Between Two Continuous Collection (in min.)	Interval Between Two Continuous Collection (in min.)	`DBSETTINGS.db_tbldcoll _time`	Specify the time for the interval (in minutes) between two collections. For data collection methods, see Data collection for the Table Details attribute group	DBSETTINGS.db_tbldcoll _time=10
¹ Database Server Properties tab ² Agent tab Run as area

Data collection for the Table Details attribute group

There are three methods to configure the agent to collect data for the Table Details attribute group:

Continuous collection

Choose this method of data collection if the SQL Server contains many tables, few large tables, or tables that are frequently updated. By using the continuous collection method, you can configure the agent to continuously collect data in the background. To enable continuous collection, select the Table Details Continuous Collection check box in the configuration window. Specify the time interval between two collections in the Interval Between Two Continuous Collection (in min.) field. The default and minimum value of this interval is 3 minutes.

Important: If you select the Table Details Continuous Collection check box, you must specify a value in the Interval Between Two Continuous Collection (in min.) field.

Scheduled collection

Choose this method of data collection if there are no frequent updates in SQL Server tables. By using the scheduled collection method, you can configure the agent to collect data at the time interval for which data collection occurs frequently. For example, if you specify all three Table Details Collection configuration settings (Day, Weekly, and Monthly), the agent starts the data collection according to the following conditions:

If Day(s) Frequency ≤ 7, the Day(s) Frequency settings are selected, and the Weekly and Monthly frequency settings are ignored.
If Day(s) Frequency > 7, the Weekly Frequency settings are selected, and the Day(s) and Monthly frequency settings are ignored.

To enable scheduled collection, clear the Table Details Continuous Collection check box and specify values for the Collection Start Time, Day(s) Frequency, Weekly Frequency, and Monthly Frequency parameters in the configuration window. The minimum time interval between two collections is 1 day.

Demand based collection

Choose this method of data collection if there are few small tables on the SQL Server. The agent collects data when the agent receives a data collection request. If the SQL Server contains many tables or few large tables, then the data collection takes time. If the data collection does not complete in the specified time frame, then no data is sent to the Tivoli Enterprise Monitoring Server. To enable demand based data collection, clear the Table Details Continuous Collection check box, and do not specify any value for the Collection Start Time, Day(s) Frequency, Weekly Frequency, and Monthly Frequency parameters in the configuration window.

Remember: If you select the Table Detail Continues Collection check box, priority is given to continuous data collection method and agent collects the data at the interval that is mentioned in the Interval Between Two Continuous Collection (in min.) field. The values that you have specified the daily, weekly, or monthly frequencies are ignored.

Feedback