This article only applies to Squared Up Version 2.0. If you're looking for help with Squared Up Version 3.0, please visit our new knowledge base

SCOM simultaneously writes data to both the Operations Manager database and the Data Warehouse database. Squared Up accesses data from the data warehouse because there is both recent and historical data stored there. So performance tuning the data warehouse is key to fast data retrieval in Squared Up.  How do you get the most out of your data warehouse performance? There isn't one configuration setting, but this article covers a five point plan for reviewing the performance of your data warehouse. 

Taken from the January 2016 Masterclass.

1. Sizing

What sort of resources does my SQL server running the data warehouse server require? As much as you can get! Before Squared Up the data warehouse was being written to, but was probably largely unused.

  • No fixed sizing rules, but the data warehouse is now a core component and will significantly influence user experience.

2. Configuration

3. Data In

SCOM is constantly writing data to the data warehouse. Check whether you do need all that data.

4. Data Retention

How long do you keep the data for?

5. Data Out

  • Scope your Squared Up dashboards - Is it useful to how a lot of data? Is is hard to interpret? Is it taking a while to load? Is this query running slowing down other dashboards?
  • Huge datasets are:
    • hard to use
    • slow to load
    • take data warehouse resources away from other users/dashboards
  • Prefer custom drilldowns over global dashboards
    • E.g. SQL server groups vs global SQL

And lastly: Make SCOM Faster!!!

User Voice  - Feed back to Microsoft:

See also:

Data Warehouse Timeout

Troubleshooting the Performance plugin