in the Zurich Release has the Collect MSSQL Components Info deprecated??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-09-2026 11:06 AM
in the Zurich Release has the Collect MSSQL Components Info deprecated?? I see that is disabled yet throws error on Discovery.
How to eradicate that to enable a clean discovery?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2026 12:42 AM
Hello @lsubramaniyan,
Please refer to the link's below:
https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-release-notes-enus.pdf
https://www.servicenow.com/docs/r/release-notes/zurich-security-notables.html
If it is helpful, please mark it as helpful and accept the correct solution by referring to this solution in the future it will be helpful to them.
Thanks & Regards,
Abbas Shaik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2026 11:55 AM
Thank you, I am still looking for more drill down particularly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi lsubramaniyan,
This is most likely not related to the pattern being deprecated, but to identification configuration.
In my case, the error was caused by using an independent identification rule on the Windows Server class, that rule did not include the MSSQL tables (mssql_components_info, mssql_sqlservice_info) in its related tables.
Because of that, the discovery engine (specifically the relation/reference step) rejected those tables with errors like 'not a known CI type", even though the tables and data existed.
Check if your identification rule, used on the Windows server class contains the following 2 related tables, if not add them and that should fix the issue.
Br,
Ronald
