- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-24-2017 12:24 PM
There now seems to be two out-of-the-box MS SQL Database classes in the CMDB. The original was cmdb_ci_db_mssql_catalog which extends the cmdb_ci_db_catalog table. If I recall correctly, I think MS SQL discovery used to put MS SQL Databases in this table.
Now there is also cmdb_ci_db_mssql_database which extends the cmdb_ci_db_instance table. It looks like discovery may now be populating this new table instead of the older catalog table.
What is the difference between these two classes that appear to be for the same thing? When should one be used over the other? Is the older catalog version of the database deprecated now, or are they both intended to be used, but in different circumstances?
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-29-2017 02:22 PM
OK, I had a call with ServiceNow. It looks like it is transitioning from the old catalog table to the new table partly due to a snafu with development. The old probe and sensor discovery model in use before Jakarta uses the old catalog table. The newer pattern based discovery model used in Jakarta will use the new table instead.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-14-2023 07:43 AM
Is there a way to group by "cmdb_ci_db_mssql_database" based on database instance table or the server on which it is hosted?
