Service Manager Data Warehouse Schema Available for Download

Chris Lauren has posted the "schema diagrams." If you're not familiar with developing management packs, writing your first few custom queries against the data warehouse can be intimidating. The database schema is based on the common management pack model, which means the relational database objects and relationships benefit from class inheritance, so you should familiarize […]

Chris Lauren has posted the "schema diagrams." If you're not familiar with developing management packs, writing your first few custom queries against the data warehouse can be intimidating. The database schema is based on the common management pack model, which means the relational database objects and relationships benefit from class inheritance, so you should familiarize yourself with the model.

No matter how many tables are in the warehouse, there are only three types of tables. It's important to understand what each type of table is used for:

  1. Dimensions represent the classes, where each row in the dimension is an instance of the class and each column is a property. Enum properties, however, are stored in "outriggers", which are like dimensions except they have one row per item in a list which describes a class instance.
  2. Fact tables are the most notable difference between a data warehouse and a transaction processing system. Generally fact tables are used to track transactions, or things that happen, over time. These transactions are usually quantified and summarized, so they get represented as metrics (called measures in data warehousing terms).

Click here to download the Service Manager 2010 Data Warehouse schema or keep reading to learn more about how to use it, here