Database Discovery

database discovery allows you to scan network subnets or existing devices to find databases such as oracle, postgresql, teradata, mysql, ms sql, hive, and more this feature enables you to automatically discover databases by accessing them with specified credentials and ports, and then add them to the appropriate device groups in your inventory to begin, navigate to devices > inventory and create device groups for each type of database you want to discover (e g , oracle, postgresql, teradata, mysql, ms sql, hive) ensure that you have a device group for every database type you intend to scan next, set up the global credentials and subnet addresses for each device group edit the device group by clicking on it and selecting edit in the direct credentials section, enter the username and password that will be used to access the databases save each property after entering the information add the subnet addresses you wish to scan by selecting subnet from the device group actions and entering the subnet information (e g , 10 20 42 1/24 to scan ip addresses from 10 20 42 1 to 10 20 42 255) now, create a discovery profile for database discovery navigate to devices > discovery and click on add discovery profile enter a name for your discovery profile, such as "ms sql discovery" for the access protocol , select database in the database credentials section, add the database names and corresponding ports you wish to discover (e g , database names like master or shinoc, and ports like 1433 or 14331) select the device groups you want to include in the discovery (e g , the ms sql device group you created earlier) set the discovery type to subnet to scan the subnets specified in the device groups enter a mail address for notification optionally, set a cron expression if you wish to schedule periodic scans save the discovery profile and click on run discovery to start the process immediately once the discovery process begins, it will attempt to access databases within the specified subnets using the provided credentials and ports if a database is successfully accessed and logged into, it will be added to the inventory under the appropriate device group, and the database credentials will be stored you can monitor the discovery process and view results in the discovery logs if there are errors—such as being unable to access a device or failing to log in—the logs will display detailed error messages when you click on specific entries this helps in troubleshooting any issues encountered during discovery oracle ms sql postgresql mysql teradata sap hana db2 cassandra hive