Database discovery connects to supported database platforms and inventories database instances. The database platforms shown are:
Microsoft SQL Server
MySQL
PostgreSQL
Oracle
MongoDB
Use this job type when you need to identify database instances separately from the servers that host them. Discovering a server through Network discovery and discovering a database instance serve different inventory purposes.
Example: A database administrator creates a Database discovery job to identify PostgreSQL instances. The infrastructure team uses Network discovery to collect information about the servers hosting those instances.
To create a new job for Database devices, perform the following steps:
Click Workspace > ITAM > Asset > Discovery > Discovery Jobs.
The Discovery Jobs list page is displayed.Click New Job.
On New Job, select the job type that matches your discovery source.
Figure: New JobJob type
Purpose shown on the selection screen
Network
Discover Windows through WMI, Linux through SSH, and network devices through SNMP.
Cloud
Enumerate virtual machines and resources across AWS, Azure, GCP, and Oracle Cloud.
Container
Discover Docker containers and Kubernetes resources.
Hypervisor
Discover guest VMs through virtualization platforms.
Database
Connect to database engines to discover instances and inventory.
Directory
Discover Active Directory information without an agent.
Storage / SAN
Discover storage systems through supported platform interfaces.
Select Database on the new job.
On Identity, select the tenant and enter a descriptive job name.

Figure: IdentityField name
Description
Tenant *
Tenant context associated with the job. The demonstration displays Information Technology.
Job Name *
Name used to identify the job in the jobs list and run details. Example: HQ Windows Inventory.
Status
Activation state selected for the job. The demonstration shows Active.
Description (optional)
Purpose, scope notes, ownership, or other context for the team.
Next
Continues to the next wizard stage.
Cancel
Leaves the wizard. Confirm any save or discard behavior presented by the application.
Click Next to open Scope.
On Scope & Exclusions, choose the scope type.
Enter the corresponding addresses. For a subnet scan, enter its CIDR block.
Add addresses, ranges, CIDRs, or hosts to exclude, one entry per line where the control is available.
Review the target boundaries and click Next.
For a branch subnet, select CIDR Subnet and enter 192.168.50.0/24. Exclude any management or sensitive targets that the network team has removed from the approved scan list. First test the worker and credentials against one representative host.Configure an address range.
Select IP Range (start - end).
Enter Start IP and End IP, for example 192.168.50.10 and 192.168.50.40.
Review any exclusions, and continue to Type.
Configure a host list.
Select IP List (multiple).
Enter the approved addresses or hostnames, one per line or separated by commas.
Check spelling, DNS resolution where applicable, and the completeness of the list.
Click Next.
Use a single host during initial validation. Expand to a list, range, or subnet only after checking that the selected worker can collect the expected data.
Figure: CIDR Scope and exclusionsField name
Description
Scope Type
Selects Single Host / IP, IP Range (start - end), CIDR Subnet, or IP List (multiple).
CIDR Block *
Subnet address and prefix for CIDR Subnet. Example: 192.168.50.0/24. Confirm the resulting range before scanning.
Start IP * / End IP *
Beginning and ending addresses for IP Range (start - end).
Exclude IPs / ranges / CIDRs / hosts (one per line)
Targets to skip within the scan scope. The UI states that excluded targets are never probed, even when they fall inside the scope.
On Type & Credentials, select the applicable Hypervisor type: VMware, Xen/Citrix, or Nutanix. You can also more than 1 types.
For each selected method, add a stored credential. Use quick creation if a suitable credential is not yet available.
Use the up and down controls to arrange the displayed execution order.
Review the methods and selected credentials, then click Next.

Figure: Protocol execution order and credentialsField or control
Description
PostgreSQL
An open-source relational database system. Select to discover PostgreSQL instances using PostgreSQL credentials.
MySQL
An open-source relational database system commonly used by web and business applications. Select to discover MySQL instances using MySQL credentials.
SQL Server
Microsoft’s relational database platform. Select to discover SQL Server instances using credentials configured for SQL Server.
Oracle
An enterprise relational database platform. Select to discover Oracle Database instances using Oracle credentials.
MongoDB
A document-oriented NoSQL database that stores data in flexible documents. Select to discover MongoDB instances using MongoDB credentials.
Create MySQL DB Credential
Enter the credential name, username, password, and port.
Click Create & Add. Confirm that the credential appears under Nutanix.

Figure: Create DB credentialField or control
Description
Credential Name *
Enter a descriptive name to identify the credential, such as PostgreSQL Production Discovery.
Database type
Select the database engine associated with the credential. The screenshot shows PostgreSQL.
Username *
Enter the database account username used to connect and collect discovery information.
Password *
Enter the password for the specified database account.
Port * (0=default)
Enter the port used to connect to the database instance. Enter 0 to use the selected engine’s default port. The screenshot shows 5432 for PostgreSQL.
SSL Mode
Select how SSL/TLS is used for the database connection. Match the selection to the database server’s connection requirements. The screenshot shows Disable.
Default Database (optional)
Enter the database to use for the initial connection, such as postgres for PostgreSQL.
Create and Add
Creates the credential and adds it to the current discovery job.
Cancel
Closes the dialog without completing credential creation.
Credential Selection Guidance
Use a dedicated account with permission to connect and read discovery metadata. Match the credential to the database engine, verify the port and SSL settings, and add fallback credentials if needed. Test access before running discovery.
The Settings screen lets you configure the database discovery job’s execution timeout, collection coverage scoring, and diagnostic capture. These options help you review discovery completeness and troubleshoot issues while managing storage use.

Figure: Settings | Collection depth
Performance
Description
Job Timeout (hours)
Sets the overall execution limit for the discovery workflow. The displayed value is 24 hours, which the screen identifies as the minimum.
Coverage Score
Calculates a per-device coverage score showing which parameters were collected and why others were not. This option is recommended and enabled in the screenshot.
Capture Engine Logs
Stores detailed discovery engine logs for each run to support troubleshooting. Enabling this option increases storage use.
Capture Per-host results
Stores detailed results for each host, accessible by IP address, for individual investigation. Disable this option to reduce storage use.
Execution and Scheduling: You can run the job using either Temporal Worker or using Discovery Engine. If you opt for Discovery Engine, it will not use the worker.
Select the execution option supported by your deployment.
For Temporal Worker, choose a worker with access to the target network. Check the Effective task queue carefully.
For an immediate validation run, leave Enable scheduled runs off and click Create & Run Now.
For recurrence, enable Enable scheduled runs and configure the interval supported by your deployed release. Verify its time basis and save behavior before activating the recurring job.

Figure: Scheduling and ExecutionField or control
Description
Temporal Worker
Executes through the discovery worker and Temporal. This option is selected and marked recommended in the UI.
Discovery Engine
Alternative local execution option shown in the demonstration.
Effective task queue
Selects the worker queue used for execution. The helper states that both scheduled runs and Run Now use only the selected worker queue.
Worker search
Searches the available worker entries when the queue selector is expanded.
Enable scheduled runs
Turns recurring execution on or off. The helper describes automatic runs at the configured interval.
Create & Run Now
Creates the job and starts an immediate run. The button is shown while scheduled runs are off.
Once you click Scan and Run Now, you will get a message mentioning Job started.

Figure: Job saved successfully