SQL Server Discovery Methods

Reading Time: 2 minutes

The article explains the discovery methods available when using UpSearch’s proprietary Microsoft SQL Server inventory Tool (‘Tool’ or ‘Application). The Data Estate Assessment is powered by this Tool, an on-premises, agentless desktop Application with a small installation footprint. The digitally signed and antivirus whitelisted Tool finds, verifies, and collects information about each Microsoft SQL Server instance and the underlying Windows Operating System.

The Tool provides four SQL Server Discovery Methods for Domain Administrators to identify and locate SQL Server instances enterprise-wide.

Main Discovery Methods

  1. Active Directory DNS
    • DNS Server: Select ‘Automatic’ or the Name/IP address of an Active Directory DNS server to query for a list of hosts with installed SQL Server instances. When ‘Automatic’ is selected, the function will use WMI queries to determine the current computer’s DNS server(s) for querying.
    • DNS Domain: Select ‘Automatic’ or specify the Active Directory domain name for querying DNS. If ‘Automatic’ is chosen, the function will use the current computer’s AD domain.
      • DNS Server: Select ‘Automatic’ or the Name/IP address of an Active Directory DNS server to query for a list of hosts with installed SQL Server instances. When ‘Automatic’ is selected, the function will use WMI queries to determine the current computer’s DNS server(s) for querying.
  1. IP Subnet: Select ‘Automatic’ or provide a list of subnets (in CIDR notation) to scan for SQL Server instances. Choosing ‘Automatic’ uses the current computer’s IP configuration to determine subnets for scanning.
  2. IP Range: Provide a list of IP ranges to be included in the inventory. If your organization uses public domains, IP Range Discovery Method is required.
  3. Computer Names: Provide a list of computer names to be included in the inventory.

Additional Discovery Options

  • Exclude Subnets: Provide a list of subnets (in CIDR notation) to exclude when testing for connectivity.
  • Limit Subnets: Provide a list of subnets (in CIDR notation) to limit the scope of connectivity tests. Only hosts within the specified subnet(s) will be included in the results.
  • Exclude Computer Names: Provide a list of computer names to be excluded when testing for connectivity. Wildcards are accepted, and IP Addresses of each computer in this list will be resolved for inclusion or exclusion.

Was this article helpful?

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact Us