What I have done is I have found that it is very handy having all our SCOM data in a data warehouse and then having it in a SSAS (SQL Server Analysis Services).

Within the zip file which can be located here below it has all the details for the following:

·         SCOM Data Warehouse and OLAP Documentation.docx

o   This has all the details required to get up and running.

·         Restore the SQL Server Database

·         Deploy your SSIS Project

·         Deploy your SSAS Project

·         Deploy your SSRS Reports

Zip File location: http://sdrv.ms/1dwycbX 

So below is some examples of what can be achieved when the data is sitting inside SSAS.

SCOM report, to analyze and predict based on the past when disks will be running out of space.

·         This utilizes the KPIs within SSAS


Using Excel we can get a trend to analyze what has been happening on a server.

·         As I am sure you are aware there are a whole host of other additions that can be added to the Excel file to make it easier for people to use such as:

o   Slicers

o   Timeline – If Excel 2013


Using Excel we can also use the KPIs that have been created to look at our Goals, Status and trends



I have also created additional reports where based on the past average of CPU % Time Used, we then compared this to the current days average if it is greater than 150% then display the data. I have then put this into SSAS Tabular and used Power View in SharePoint in order for guys to quickly see the data.

I have tried to ensure that everything should work as expected.

If there are any issues or something that does not work, please contact me in the contact section below.

I do hope that this will be as useful for you as it has been and continues to be for me.

0 thoughts on “SCOM (Systems Center Operations Manager) Cube and Data warehouse”

  1. I am trying to use code having issues. Backup is incompelte. Please upload compelted backup.


    1. Hi there

      Are you restoring the database backup to a SQL Server 2012?

      Also I am assuming you are referring to the SQL BAK file?

      If you can also confirm that you have changed the correct locations for your data and log files?


  2. Hi Gilbert. I’ve installed everything, and now trying to run the SSIS packages. The daily is failing trying to update the maxdatekey table because the value is null. Do I need to seed the table somehow?

    Also, we don’t have enterprise edition SQL, so needed to make a few changes to the database (remove compression) and the cube (remove partitions). But I don’t think either one of those things would be causing this problem — I hope. 🙂

      1. Hi there, I thought I would reply to this second comment.

        I am glad that you figured it out, and I did think that I put in an IsNull for the MaxDateKey, but I could have missed that.

        Yes removing the Compression, as well as the partition information should not be a show stopper and enable you to get it working and up and running.

        If you still run into any issues please let me know I will assist where I can.


  3. could you please provide some input about what type of logic is used in this Cube to get the prediction data. what is the calculation? we managed to deploy cube successfully. even we are getting sample report. but its not giving data for all machines. appreciate your inputs.

    1. Hi there,

      The logic should be in the report, where it has the MDX statements on how to use Linear regression?

      Let me know if that makes sense.

      And with regards to scheduling a job, due to you using an MDX query, it will complete the calculations when you run the report based on your data in the cube.


Leave a Reply

Your email address will not be published. Required fields are marked *