Skip to main content
The Microsoft SQL Server scan module captures SQL Server instances and their databases. It requires a connected gateway.

Captured data

The scan creates assets of these two types: How the detail pages of the types are structured is described in Databases.

Setting up the job

The wizard follows the standard path Basics › Targets › Schedule › Summary—see Creating a Scan Job. The Targets step is what sets this module apart. Each row carries four columns: The Credentials column may stay empty. The scan then runs under the gateway’s service account, and that account needs the rights under Permissions. An entry in Credentials for all targets applies to every row without an assignment of its own. The scan captures system databases only when the module setting Collect System Databases is on; it is off by default. Where the module settings are is described in Creating a Scan Job.

Prerequisites

Ports and protocols

Permissions

  • For a complete scan, the account has the sysadmin server role.
  • Without sysadmin, the scan captures only parts of the server or the instance.

Network requirements

  • The firewall allows the ports above.
  • Database and server allow remote connections.
  • The TCP/IP protocol is enabled for the SQL Server or the instance.
After it is created, the job appears among the jobs; how you watch and adjust it is in Managing Jobs. The ports of all scan modules are in the Scan Reference.