Before you can begin using the management pack, you must create an adapter instance to identify the host from which the management pack will retrieve data. Optionally, vRealize Orchestrator users can automatically create an adapter instance using our vRO workflow. See our Customer Support Team's knowledge article:Creating SQL Server Adapter Instances with vRO for more information.

Procedure

  1. From the top navigation bar, select Administration. In the right panel, the Solutions view will be displayed.
  2. Select Microsoft SQL Server from the Solutions list on the right.

    solutions_list_after_install-3
  3. Click the Configure configure_icon icon. The Manage Solution window will appear.
    Note: Click the Add add_icon icon above the Instance Name list on the left to create multiple adapter instances.

    manage_solution_window-2
  4. In the Manage Solution window, enter the following information:
    1. Adapter Settings:
      • Display Name: Enter a name for this particular adapter instance of the management pack.
      • Description: Optional field, but it can be helpful to describe multiple adapter instances.
    2. Basic Settings:

      • Host:Enter one of the following, depending on whether you're configuring a standalone or clustered SQL Server:

        • Standalone Configuration: Hostname (or IPv4 address) of your MS SQL Server instance

          Important: IPv6 addresses are not supported.
        • Clustered Configuration: Virtual IP (VIP), or hostname for the VIP, of your MS SQL Server instance

          Important: For full coverage of Always On Availability Group health and status, create separate adapter instances pointing to each individual replica (host) and ensure Autodiscovery is set to True. This will allow the management pack to monitor both the primary and secondary replica health statuses, and provide as much visibility as possible.
      • Instance: Enter the name of the MS SQL Instance that is running; default name is MSSQLSERVER.
      • Credential: Select the credential you created when Creating a Credential (Microsoft SQL Server), or you can create one now by clicking the add_icon icon.
    3. Advanced Settings:
      • Collectors/Groups: Default Collector/Group is automatically selected. Click the drop-down menu if you want to run the collection on a different node.
      • Port: Optional; defaults to instance port 1433. If using a different port, specify it here.

        Important: If using dynamic ports, you will want to change the default port to SQL Server Browser Service UDP port 1434. For more information, see Microsoft's Configure the Windows Firewall to Allow SQL Server Access documentation topic.
      • Maximum Query Resources: Specify the maximum number of queries to keep in your vROps environment; default value is 100.
      • Active Query Resources: Specify the number of queries to return per collection; default value is 10.
      • Maximum Wait Time Resources: Specify the maximum number of wait time resources to keep in your vROps environment; default value is 100.
      • Active Wait Time Resources: Specify the number of wait time resources to return per collection; default value is 10.
      • SSL Config: Default setting is No Verify (SSL enabled/certificate not verified); other choices include No SSL(SSL disabled) and Verify (SSL enabled/certificate is verified). See: Adding an SSL Certificate to the vROps Truststore (Microsoft SQL Server).
      • Use NTLM V2: Set to True to enable NTLM v2 authentication; default value is False.
      • Thread Pool Size:Specify the maximum number of concurrent threads you want to have running for collection, keeping in mind the performance impact of more concurrent threads. Default value is 16 threads.
      • Connection Pool Size:Specify the maximum number of concurrent connections, keeping in mind the performance impact of more concurrent connections. Default value is 16 connections.
      • Thread Timeout (Seconds):Default timeout is 30 seconds. If you anticipate your calls taking longer than the default setting, adjust accordingly. 

        Caution: If your Microsoft SQL Server is an AlwaysOn deployment, the default timeout value of 30s may be insufficient. Raising it to 240s should resolve any collection issues due to this problem. Note also that raising the timeout does not cause collection to take any longer, it just gives it more time in which to complete. In addition, increasing the Thread Pool Size should help performance if you are running into collection timeout problems.
      • Exclude All Events: Default value is False; set to True to exclude events marked with an asterisk in the Alerts (Microsoft SQL Server) table (overrides Exclude Only Log-Based Events setting below).
      • Exclude Only Log-Based Events: Default value is False; set to True to exclude only log-based events.
      • Support Autodiscovery: Default setting is True.
  5. Click Test Connection to test the configured connection information.
  6. Click Save Settings and Close to save your adapter instance.

What to do next