Unable to discovery MS SQL instance

[Alok Kr Gupta]

Hi All,

I am trying to discover SQL instance and there are many instance are discovered successfully into MSFT SQL Instance table  (cmdb_ci_db_mssql_instaance) .

However, I am still not able to discover many instance which are active. There is also a scenario where I am able to discover one instance on a host, however not able to discover another installed on the same host as well.

I am currently validating below,

• Validate if ServiceAccount is still  is part of local admin group for targeted servers.
• Check if .Net (v3.5 & 4, or 4.5) , Powershell, Common Language Runtime, MS SQL Management library is installed on MID Server.
• Verify if SMO library is loaded on MID server.
• Check if MID server  has the necessary permissions to read the Windows Registry on a remote mode
• Verify remote read-only access to the following WMI namespaces:

• Root\CIMv2
• Root\Microsoft\SqlServer\ComputerManagement*

However request if anyone can help and let me know if anything else needs to be checked or am I missing out on something ?

[Runjay Patel]

Hi @Alok Kr Gupta ,

Seems you have done all possible troubleshooting for ms sql, SMO 2.0 or above has to be installed on mid server. 
what error are you getting ? Or mssql pattern itself are not getting triggered? If that so check the port number on which sql installed and ask network team to open it if it is blocked.

Accept the solution if it helped.

[Alok Kr Gupta]

Thanks Runjay for your response.

Let me give your a scenario here where you could help.

I have a machine on which 6 SQL instances are running.

Via discovery I could see 4 out of those 6 being discovered and created in MSFT SQL Instance class. 

I ran a quick discovery of the server again and in the ECC input XML, I could see all those 6 instances ( including 2 which are not in sql instance table).

Can you point out the reason? I do not see any error message in the job logs

[Runjay Patel]

Hi @Alok Kr Gupta ,

Check below.

• Filter Conditions in Discovery Patterns: Ensure the Discovery pattern or probe processing script is not excluding these instances due to conditions like specific version checks, naming conventions, or attribute filters.

• Duplicate Reconciliation Rules: Reconciliation rules might have treated the missing instances as duplicates or merged them with existing records based on a duplicate CI identification logic.

• Discovery Errors: Look for errors or warnings in the Discovery logs (Discovery Log module) to check if these instances failed during the classification or identification phases.

• Probe/Classifier Limitations: Ensure the probe/trigger rules are correctly configured to identify all instances. Review the MID Server’s capabilities and configuration if any limitations are observed.

• Ignored CIs: Check if these instances are being ignored based on Discovery's exclusion rules or manual suppression.

-------------------------------------------------------------------------

If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.

Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay

-------------------------------------------------------------------------

[Tony Branton]

Discovery is part of the ITOM portfolio, not the CMDB. In future please post questions related to Discovery in the ITOM forum.