FAQ

You can use the following two step procedure to verify whether the Windows user used in the configuration, has the right permissions for monitoring.

Step 1:

The Windows integrated security user is used to launch the MS SQL KM external process (SQLCollector.exe). This user should have the right permissions to launch the executable located under the <PATROL_HOME>\mssql\x64 directory.

To verify the permissions, use the ‘Runas’ command line utility with the following format: runas /user:<localmachinename>\administrator cmd

1. Open the command prompt from the <PATROL_HOME>\mssql\x64 directory.
2. Type the following:
   Runas /user:<localmachinename>\administrator “SQLCollector.exe –env TestUser”
   For example:
   
   And click enter.
3. Enter the password.
    
4. In case of failure, the following message is displayed:
    
5. |When successful, the KM name with version is displayed in a new window. This indicates that the Windows integrated security user had the right permissions to launch the external process.
    
6. Close this window, 

Step 2:

After successful completion of Step 1, proceed with Step 2.

Run the MS SQL KM external process in the diagnostic mode to verify the connection with the remote host. If the Windows user is an integrated security user, launch the SQLCollector.exe process with the ‘Runas’ utility.

1. Open the command prompt from the <PATROL_HOME>\mssql\x64 directory.

2. Type the following command:
   SQLCollector.exe -diag check_host_conn
   or
   Runas /user:clm-aus-003666\administrator “SQLCollector.exe – diag check_host_conn” (if the Windows user is an integrated security user)

    Output window for BMC PATROL for Microsoft SQL server 9.6.11 and before. Click here to expand.

   

    Output window for BMC PATROL for Microsoft SQL server 9.6.12 and later. Click here to expand.

   

3. The connection and the discovery status are displayed:
   For example: Success connection to the remote host using the Windows user, but there are no MS SQL Server instances on this host:

    Output window for BMC PATROL for Microsoft SQL server 9.6.11 and before. Click here to expand.

    

    Output window for BMC PATROL for Microsoft SQL server 9.6.12 and later. Click here to expand.

    

You must log in the monitored MS SQL Server instance using the SQL Server Management studio.

You can use the following procedure to check the host name or IP address: 

1. Ping the Host name/IP address from the PATROL Agent machine.
2. Run the MS SQL KM external process in the diagnostic mode to verify a connection to the remote host. For more information, see How do I check whether the Windows user used in the configuration, be used for monitoring? 

You can use any regex validator to verify the regular expressions.

For example: The following MS SQL Server instances are installed on one clm-test-1234 host:
clm-test-1234
clm-test-1234\M1
clm-test-1234\Mirror

For monitoring only:
clm-test-1234
clm-test-1234\M1
enter the following regex in MS SQL server instance name (regex) field:
clm-test-1234|clm-test-1234\\M1

You can use the following procedure to filter the MS SQL Server databases:

1. In the Databases Filtering Options section, set Include in the Filtering mode field.
2. Set the relevant regex in the Include/Exclude from monitoring (regex) field.
   For example: To monitor only ‘master’ DB, set ‘^master$’ regex.

You can enable PSL logging using any of the following options:

Configuring in BMC PATROL Consoles:
Right-click the MSSQL node > Knowledge Module Commands > Logging PSL > Enable

Configuring in BMC ProactiveNet Central Monitoring Administration console:
In the ‘Global administration settings’ section, select the Logging checkbox.

Step 1:

Configuring in BMC PATROL Consoles:

1. To enable the MS SQL KM external process (SQLCollector.exe) logging, right click the MSSQL node > Knowledge Module Commands > Environment Configuration
2. Select the relevant Environment to modify or choose to add new Environment.
3. From the Environment Configuration dialog box check the ‘Logging’ checkbox.
4. Save the changes

Configuring in BMC ProactiveNet Central Monitoring Administration console:

1. In ‘KM administration’ section, enable MS SQL KM external process (SQLCollector.exe) by checking the ‘Logging’ checkbox.

2. Save the changes. 

   Note

   Step 2 is not required for versions 9.6.12 and later.

Step 2:

1. Open the file ‘NLog.config’ located under <PATROL_HOME>\mssql\ configuration directory.
2. Change the line:
   <logger name="*" minlevel="Error" writeTo="All"/>
   to:
   <logger name="*" minlevel="Debug" writeTo="All"/>
3. Save the file

To know which version of .NET framework supports the KM, see System requirements.

To determine which .NET Framework versions are Installed, see the Microsoft documentation. 

Configuring in BMC PATROL Consoles:

1. To change default collection interval for the environment, right click the MSSQL node > Knowledge Module Commands > Environment Configuration
2. Select the relevant Environment to modify or choose to add new Environment.
3. From the Environment Configuration dialog box change the ‘Data collection interval’ field.
4. Save the changes.

Configuring in BMC ProactiveNet Central Monitoring Administration console:

1. In ‘KM administration’ section, change the ‘Data collection interval’ field.
2. Save the changes

Discovery

This diagnostic simulate creates/updates/removes of SQL instance under host. To start discovery diagnostic run the next command: SQL_Collector.exe diag discovery

Host connection

This diagnostic simulate connection to local/remote host and if credentials are ok to gather required info from host. To start host connection diagnostic run the next command: SQL_Collector.exe diag host_connection

Machine information

This diagnostic simulate connection to local/remote host and asking for info from connected host. To start Machine info diagnostic run the next command: SQL_Collector.exe diag machine_info

No. You can upgrade single KM also.

In BMC Helix Operations Management, to use the new configurations added to the policy in the upgraded KM, you will clone the policy and create a new one by using the cloned policy.

In TrueSight Operations Management, you can change the KM version in an existing policy and configure the new configurations added in the upgraded KM.

In both the cases, you can also leave the existing policies as is and create a new policy to utilize the new features.

You will continue to see the collected data under the device that you configured for collection. If you ensure similar device configurations in the new policies, the new collected data will also show under the same device.

You do not need to update the exisitng thresholds. However, set up thresholds for new attributes added to a release.

You do not need to set up event policies for existing attributes. However, set up new event policies or update the existing ones for new attributes added to a release.