Please let me know what knowledge you have written about OOTB table definitions in CMDB.

[M_Tomy]

Dear Expert

Please let me know what knowledge you have written about OOTB table definitions in CMDB.
They want to know schema information and detailed table entry definitions.
My colleague wants to know.
I have no knowledge of CMDB and would appreciate your help if you do.
If possible, I would like to know where ServiceNow's Docs are listed.
Or even the Knowledge of Now community is fine.

Target table

・cmdb_ci
・cmdb_ci_hardware
・cmdb_ci_computer
・cmdb_ci_server
・cmdb_ci_win_server
・cmdb_ci_disk
・cmdb_ci_file_system
・cmdb_ci_network_adapter
・cmdb_running_process
・cmdb_ci_spkg
・cmdb_software_instance
・cmdb_ci_db_mssql_instance
・cmdb_ci_db_mssql_database

Best regards.

[Sandeep Rajput]

@M_Tomy This is what AI has to say about the tables listed in your question.

Core CMDB Tables

1. cmdb_ci
   • Purpose: Parent table for all Configuration Items (CIs).
   • Use Cases: Stores generic CI information such as name, category, and status. All other CI-specific tables extend from this table.

---

Hardware and Computing CIs

2. cmdb_ci_hardware

   • Purpose: Extends cmdb_ci and stores hardware-specific CIs.
   • Use Cases: Tracking physical devices like desktops, laptops, and peripherals.

3. cmdb_ci_computer

   • Purpose: Extends cmdb_ci_hardware and stores computing devices.
   • Use Cases: Used for general computers, regardless of being servers, workstations, or other types.

4. cmdb_ci_server

   • Purpose: Extends cmdb_ci_computer and represents server devices.
   • Use Cases: Tracks physical and virtual servers, storing attributes like CPU, memory, and OS.

5. cmdb_ci_win_server

   • Purpose: Extends cmdb_ci_server and is specific to Windows servers.
   • Use Cases: Tracks detailed configurations and versions for Windows-based servers.

---

Storage and File Systems

6. cmdb_ci_disk

   • Purpose: Represents physical or virtual disks in the infrastructure.
   • Use Cases: Tracks disk-specific details such as capacity and type.

7. cmdb_ci_file_system

   • Purpose: Represents file systems within a CI.
   • Use Cases: Tracks storage configuration, partition details, and utilization for servers and storage devices.

---

Networking Components

8. cmdb_ci_network_adapter
   • Purpose: Represents network adapters associated with CIs.
   • Use Cases: Tracks details like IP addresses, MAC addresses, and connection status for network-enabled devices.

---

Processes and Software

9. cmdb_running_process

   • Purpose: Stores information about running processes on devices.
   • Use Cases: Used for operational monitoring and performance analysis.

10. cmdb_ci_spkg

    • Purpose: Represents software packages installed on CIs.
    • Use Cases: Tracks software package details like version and vendor.

11. cmdb_software_instance

    • Purpose: Represents instances of software running on a CI.
    • Use Cases: Tracks relationships between software and the host CI, such as installations and usage metrics.

---

Database-Specific Tables

12. cmdb_ci_db_mssql_instance

    • Purpose: Represents instances of Microsoft SQL Server.
    • Use Cases: Tracks SQL instance-specific information like configurations, ports, and resource utilization.

13. cmdb_ci_db_mssql_database

    • Purpose: Represents individual databases within an MS SQL Server instance.
    • Use Cases: Tracks database-specific information like schema, size, and status.

---

Key Points:

• Hierarchical Structure: Most CMDB tables extend from a parent class, inheriting common attributes.
• Relationships: These tables often have relationships with one another (e.g., a server (cmdb_ci_server) can host software instances (cmdb_software_instance) and databases (cmdb_ci_db_mssql_database)).
• Customization: You can extend or customize these tables to meet specific business requirements.

[Anand Kumar P]

Hi @M_Tomy ,

1. cmdb_ci:

Stores general configuration item (CI) records, serving as the base table for all CIs in the CMDB. It provides common fields inherited by all CI-specific tables.

2. cmdb_ci_hardware:

Focuses on physical hardware CIs such as desktops, laptops, and other devices. It extends the cmdb_ci table to store hardware-specific attributes.

3. cmdb_ci_computer:

Contains records for computing devices like PCs, workstations, and laptops. Tracks details like operating systems, CPU, and memory.

4. cmdb_ci_server:

Holds records for server CIs, including physical and virtual servers. Stores attributes like server type, CPU, and storage capacity.

5. cmdb_ci_win_server:

A specialized table for Windows-based servers, extending cmdb_ci_server to include Windows-specific attributes.

6. cmdb_ci_disk:

Tracks details about storage disks associated with servers or computers, including disk size and usage.

7. cmdb_ci_file_system:

Stores information about file systems in servers or devices, such as mount points, capacities, and file types.

8. cmdb_ci_network_adapter:

Holds data about network adapters, including MAC addresses, IP configurations, and connection speeds.

9. cmdb_running_process:

Contains details about active processes running on devices, including process names, resource usage, and status.

10. cmdb_ci_spkg:

Stores information about software packages installed on devices, including package names and versions.

11. cmdb_software_instance:

Tracks individual instances of software running on devices, such as applications or services.

12. cmdb_ci_db_mssql_instance:

Contains records for Microsoft SQL Server instances, storing details like instance names, versions, and configurations.

13. cmdb_ci_db_mssql_database:

Holds data on individual Microsoft SQL Server databases, including database names, sizes, and status.

Mark it as helpful and solution proposed if it serves your purpose.
Thanks,
Anand

[M_Tomy]

SUPPLEMENTARY.

We are not interested in the definitions of the tables themselves, but in the definitions and schema of the items in each table.
Sorry, my writing style is not good.
The text has been corrected.

[Sandeep Rajput · Accepted solution]

@M_Tomy Here is how you can get schema and attribute information.

Navigate to Tables and Columns module in filter navigator.  Search your table and click on Schema map

Schema map will be shown to you.

Hope this answers your question