Citrix: Configuring SCOM Aggregation Retention Times for XenApp/XenDesktop
Reports in Citrix SCOM Management Packs use the Operations Manager data warehouse database (OperationsManagerDW) as a source for graphical representation of data in a useful way. Often, you might be confronted with a situation for which the retention needs to be adjusted for a specific environment. The problem is that OperationsManagerDW can be one of the largest databases, so retaining its data—especially redundant data—could turn out to be very costly.
Let’s talk, today, about how configuring aggregation retention times in the OperationsManagerDW can help remove unnecessary data and SCOM maintain performance.
OperationsManagerDW is a Microsoft SQL Server database that stores monitoring and alerting data for historical purposes. The most important function of OperationsManagerDW is reporting. This is possible because of the availability of long-lasting data. Data gets stored in both the operational and data warehouse databases. However, only in the data warehouse database it is retained for extended periods of time. Custom data is also stored only in the data warehouse database. It is possible to store performance and event data in either the operational or data warehouse databases.
Citrix SCOM Management Packs first store raw data in OperationsManagerDW, by default every 5 minutes. Raw data is then processed and stored as aggregated hourly and daily data. Hourly aggregation takes all the samples from the last hour, calculates the minimum, maximum, average and standard deviation values and then stores them in a separate hourly aggregation table. Daily aggregation also takes raw samples, but from the last 24 hours.
Read the entire article here, Configuring SCOM Aggregation Retention Times for XenApp/XenDesktop
via the fine folks at Citrix Systems, Inc.