Need help on Discovery for DB instances

[Deepika Jain]

Hi,

I am new to discovery and I want to discover the database instances(MS SQL).

Can anyone help me with some step by step process for the DB discovery.

Currently I only know that we have OOTB Tables and we have OOTB Patterns as well and we need applicative credentials for the particular DBs and follow the normal process of the discovery schedule and running the schedules, I am not sure if it's right process or not.

Any Help would be appreciated.

Thanks in Advance!

[Doci1]

yes, you need credentials, access to the target and basically that is it. All DB discovery is process automatically as OOTB.

[Harish Bainsla]

Hi @Deepika Jain  please check below link

https://www.servicenow.com/docs/bundle/yokohama-it-operations-management/page/product/discovery/conc...

https://www.servicenow.com/docs/bundle/yokohama-it-operations-management/page/product/discovery/conc...

https://www.servicenow.com/community/itom-forum/how-to-discover-database-instances/m-p/949096

if my answer helps you mark helpful and accept solution

[Selva Arun · Accepted solution]

Hi Deepika,

 It’s great that you're getting started with discovering Microsoft SQL (MS SQL) instances. Below is a step-by-step process to help you and the steps have been summarized from https://www.servicenow.com/docs/bundle/yokohama-it-operations-management/page/product/discovery/refe...

1. Check Prerequisites:

   • Ensure that the Discovery and Service Mapping application is up-to-date.
   • Verify that the MID Server is installed and configured properly on the network, and it has connectivity to the target servers.

2. Set Up Credentials:

   • For MS SQL discovery, you will need Windows credentials to access the Windows server and SQL credentials (for SQL authentication) to access the MS SQL Server instance.
   • The MID Server needs permissions to read the Windows Registry and execute WMI queries for discovering SQL Servers.

3. Use the OOTB Patterns:

   • The MSSQL DB on Windows pattern is available out-of-the-box (OOTB) and will help you discover the SQL server instances.
   • Make sure that you use the correct SQL authentication for each database.

4. Discovery Configuration:

   • If you need to discover SQL Failover Clusters or Always On availability groups, you may need to enable certain settings for those.
   • You will also need to configure the pattern to detect MSSQL Cluster information.

5. Run Discovery:

   • Once the pattern and credentials are set up, schedule your discovery to run at appropriate intervals. The system will automatically discover SQL Instances, Databases, and Clusters.
   • Ensure that the discovery is triggered correctly by running the sqlservr.exe process on your server.

6. Review the Data:

   • After discovery, review the data collected in the CMDB for SQL instances, databases, and related cluster nodes.
   • You will see relationships created between MSSQL Instances, Windows Servers, and Databases.

7. Handling Duplicate Instances:

   • In case of failover or cluster nodes, you may encounter duplicate instances. You can choose to keep or delete them based on your setup.

8. Automate Discovery:

   • Once everything is configured, you can schedule periodic discovery jobs to ensure the database and server records are always up-to-date.

By following these steps, you should be able to discover MS SQL instances and their related databases effectively. The process you mentioned about using OOTB tables, patterns, and scheduling discovery is correct, and you'll be all set to go!

Feel free to ask if you need more details or if something is unclear.

Good luck!

If you believe the solution provided has adequately addressed your query, could you please **mark it as 'Helpful'** and **'Accept it as a Solution'**? This will help other community members who might have the same question find the answer more easily.

Thank you for your consideration.

Selva

---

[Deepika Jain]

Thanks for the answer, 

Marking it Helpful.