Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

MSSQL server discovery

Log in to subscribe to topics and get notified when content changes.

MSSQL server discovery

Discovery identifies and classifies information about MSSQL servers on Windows machines.

A pattern performs the discovery of MSSQL instances. This pattern replaces the Windows - MSSQL probe for new instances. If you want to continue to use probes, you can deactivate the Horizontal discovery probe, which launches the pattern, and then activate the necessary probes.
Warning: DO NOT switch from probes to patterns if you are already running Discovery with probes, and your CMDB is already populated. If you do so, it is possible that the pattern Discovery process does not synchronize on the same values that the probe Discovery process does. This could result in duplicate CIs in your CMDB.


Configure these credentials:
Credential type Additional notes


Applicative credentials
The credentials need public access to the following:
  • The target Windows host.
  • The Microsoft SQL Server instance on the target Windows host. You must add the user to the SQL Server configuration.
  • The MID Server host. The SMO libraries locally impersonate the credentials for the target system prior to connecting to the Microsoft SQL Server. This behavior is enforced by Active Directory. Authentication only succeeds if the domain requirements specified here are met.
  • Role: On MS SQL 2014 and 2016, the sysadmin role must be assigned to the user to obtain the instance version. The public role does not have permission to retrieve the instance version.
    Note: If there are no matching discovery credentials, probes may attempt to connect using the MID Server service credentials. The MID Server service credentials are only valid if the MID Server host is on same domain as the Microsoft SQL Server host.

Specify the CI type on the credential as MSFT SQL Instance.

Windows credentials The credentials need access to the following:
  • A database user that can access these MSSQL tables: sys.dm_exec_sessions and sys.dm_os_schedulers, SERVERPROPERTY.
  • The CI Type MSFT SQL Instance.

Classifier, pattern, and probe

Discovery uses these classifiers, probes, and patterns for SQL discovery:
Classifier Trigger probes Pattern
Microsoft SQL Server
  • Horizontal discovery probe: launches patterns
  • Windows - MSSQL*
MSSql DB On Windows Pattern
*Probes inactive on new instances.

Verify that the correct pattern is specified in the horizontal pattern probe on the classifier. See Add the Horizontal Pattern probe to a classifier for instructions.

Data collected

The running processes of the database (the actual SQL server) is referred to as the database instance. The following data is collected in the MSFT SQL Instance [cmdb_ci_db_mssql_instance] table:

Label Field name
Name name
Instance instance_name
TCP port tcp_port
Portdynamic port_dynamic
Version name version_name
Edition edition
Version version
Engine edition engine_edition
Install directory* install_directory
CPU sockets* cpu_sockets
Service Pack* service_pack
*These fields are populated by the pattern only.
The database is referred to as the catalog. The following data is collected in the MSFT SQL Catalog [cmdb_ci_db_mssql_catalog] table:
Note: Only the Windows - MSSQL probe, not the MSSql DB On Windows pattern, populates this table.
Label Field name
Name name
Status status
Note: You can find the data for the actual server on which the MSSQL instance and catalogs resides in the Windows computer [cmdb_ci_win_server].
Discovery populates the MSSQL database [cmdb_ci_db_mssql_database] table with the MSSql DB on Windows Pattern:
Label Field name
Name name
Operational status operational_status

For Microsoft SQL2000 servers, Discovery can match instance names to their process ID.

When Software Asset Management is activated, all discovered software is saved in at least two places in the CMDB: in the Software Installation [cmdb_sam_sw_install] table and the tables specific to the application type. A reference field is provided on these application-specific tables to the corresponding record in the Software Installation table.