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.
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.
Use Tao’s Health Check OpsMgr 2012 Data Warehouse Health Check Script.
Any more tips? Feedback to Tao.
3. Data In
SCOM is constantly writing data to the data warehouse. Check whether you do need all that data.
Tune collection intervals - Do you need high frequency granular performance metrics? If not, perhaps tune down the collection intervals.
Disable unnecessary rules - Disable any rules that are not useful to your organisation. Send Squared Up links out asking colleagues if they want to see that data, or if anything is missing.
- Check also for noisy monitors “flip-flopping” - It's not just performance data, every health state change is written to the operations manager database and the data warehouse, so if there are monitors that are changing from green to red frequently, find those monitors and tune the thresholds, or disable the monitors, to save all those write actions. See https://blogs.technet.microsoft.com/kevinholman/2009/12/21/tuning-tip-do-you-have-monitors-constantly-flip-flopping/
https://community.squaredup.com/browse/download-info/scom-sql-queries-kevin-holman/ A good place to start, and a link to Kevin Holman's blog, many queries that might help you tune your environment.
4. Data Retention
How long do you keep the data for?
- Do you need all that hourly data? It's not just about the capacity of the data warehouse for storing the data, but more the performance, in terms of the SQL server's memory. If hourly data is available for a year, then users may well be querying it and pulling all that data back. Consider reducing the amount of hourly data retained.
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: