Whether you need to create a custom report, or a custom computer filter based on Inventory Data in Inventory Solution 7.0, knowing the database schema is important. In Inventory Solution 7.0 the data structure for inventory has been completely revamped. If you are familiar with the data structure for Inventory Solution 6.x, or if you are new to Inventory Solution in version 7.0, this document provides technical details on the new data structure. In Part 1 the Operating System data classes will be covered.

Introduction

Documenting database schema is not an easy task. SQL can provide a table-column view of all selected tables, but this does not account for any interdependencies between tables in a normalized environment. In 7.0 Normalization includes dependencies on base-class tables, or, in other words, subsequent tables are extensions of the base table.

Database Schema

The following list reveals data classes and their structure. First, the name of the table is given, followed by a designation as a Base or Sub Class data class. The following label system is used:

• BASE Class - This is a data class that has no dependencies on other Inventory data classes
• SUB Class - This is a data class that has 1 dependency on a BASE data class
• TERTIARY Class - This is a data class that has two dependent data class in the hierarchy (Not used for Operating System data classes)
• STANDARD Class - This is a data class that contains no dependencies or sub classes

Note the following when reviewing the grids:

1. Display Name represents how the column will be labeled when working within the Symantec Management Console, including reports, Resource Manager details, Pickers, etc.
2. Not all values have descriptions, but the label of the table and column should provide data on what's stored therein.
3. When a BASE Class is listed, all subsequent SUB or TERTIARY classes subsequently listed are tied to that BASE Class, sequentially, below.
4. Qualifiers per Column/Value are provided based on applicability.

For help in navigating dependent data classes, use the following guide:

• Altiris_OS_OperatingSystem
  • Altiris_OS_OperatingSystem_Windows
• Altiris_OS_FileShare
  • Altiris_OS_NFSShare
• Altiris_OS_Job
  • Altiris_OS_Job_Unix
  • Altiris_OS_Job_Windows

Altiris_OS_OperatingSystem - BASE Class

Altiris_OS_OperatingSystem_Windows - SUB Class

Dependent on Altiris_OS_OperatingSystem

Altiris_OS_FileShare - BASE Class

Altiris_OS_NFSShare - SUB Class

Altiris_OS_Job - BASE Class

Altiris_OS_Job_UNIX - SUB Class

Altiris_OS_Job_Windows - SUB Class

Standard Classes

The following data classes are considered Stand-alone.

Altiris_OS_ACLs_Windows - STANDARD Class

Altiris_OS_ActiveTcpUdpPorts - STANDARD Class

Altiris_OS_AdminGroupMembers - STANDARD Class

Altiris_OS_InventoryResults - STANDARD Class

Altiris_OS_MDAC_Windows - STANDARD Class

Altiris_OS_NetworkProvider_Windows - STANDARD Class

Altiris_OS_ODBC_Windows - STANDARD Class

Altiris_OS_Patches_Windows - STANDARD Class

Altiris_OS_Service_Windows - STANDARD Class

Altiris_OS_Shares_Windows - STANDARD Class

Altiris_OS_SystemDevices_Windows - STANDARD Class

Altiris_OS_TaskScheduler_Windows - STANDARD Class

Altiris_OS_Timezone - STANDARD Class

Conclusion

Hopefully this provides a guide that will allow you to upgrade or implement Inventory Solution 7.0 armed with the necessary data to manage your reports, filters, or anything else based off of Operating System data.

Inventory Solution 7.0 Database Schema - Index of Articles

Inventory Solution 7.0 Database Schema, Part 2: Hardware Inventory