Granular Reporting in System Center Operations Manager

Granular Reporting in System Center Operations Manager


Please click the +1 button if you find this post helpful.



The default reports in SCOM 2012, generate using either Daily or Hourly aggregate data. If you find yourself in a situation where you need a more granular level of report detail for a short window of time, then you'll need to create custom reports. The good news is that the raw data is kept in the Data Warehouse. Once you define a new dataset using the vPerfRaw view instead of the Hourly/Daily views, then you're in business. Keep in mind that this information is only ever used by SCOM to generate the AverageValue data used in the Hourly/Daily views, so it is only kept for two days by default. This retention period can be changed, but it's not reccomended unless you fully understand the impact it will have on both performance and database size.

Here is a quick snippit of T-SQL used to generate a dataset to query for % Processor Time stored in the vPerfRaw view.

SELECT Perf.vPerfRaw.DateTime, Perf.vPerfRaw.SampleValue, vManagedEntity.Path, vPerformanceRule.ObjectName, vPerformanceRule.CounterName,
vManagedEntity.FullName, vPerformanceRuleInstance.InstanceName
FROM vPerformanceRuleInstance INNER JOIN
Perf.vPerfRaw ON vPerformanceRuleInstance.PerformanceRuleInstanceRowId = Perf.vPerfRaw.PerformanceRuleInstanceRowId INNER JOIN
vManagedEntity ON Perf.vPerfRaw.ManagedEntityRowId = vManagedEntity.ManagedEntityRowId INNER JOIN
vPerformanceRule ON vPerformanceRuleInstance.RuleRowId = vPerformanceRule.RuleRowId
WHERE (vPerformanceRule.CounterName = '% Processor Time') AND (vManagedEntity.Path = @ComputerName)
ORDER BY Perf.vPerfRaw.DateTime




Windows 2008 R2 Server,System Center Operations Manager 2012, SCOM, Reporting, T-SQL, Query, Data Warehouse, Perfmon, Performance Monitor, SQL Server, SSRS

Executive Summary - Planning for Reporting Services


Executive Summary - Planning for Reporting Services

System Center Operations Manager 2012


Please click the +1 button if you find this post helpful.



The below is an executive summary for requirements planning for implementing Reporting Services for System Center Operations Manager 2012.

Reporting Data Warehouse

  • 400 day default data retention period.
  • Data is entered in to the data warehouse real time (versus previously batched).
  • Performance of I/O subsystem is vital, as well as proper capacity planning.
  • There is only one Reporting data warehouse per management group.
  • The minimum supported hardware configuration for the Reporting data warehouse component is as follows:
    • 2.8GHz or faster x64 processor
    • 4GB of RAM or more
    • 100GB of available hard disk space
  • The software requirements for the Reporting data warehouse component consist of the following:
    • Windows Server 2008 SP2 64 bit or Windows Server 2008 R2 SP1
    • SQL Server 2008 SP1 or higher
    • SQL Server 2008 R2 or higher
    • .NET Framework 3.5 SP1
    • .NET Framework 4.0
    •  SQL Collation—SQL_Latin1_General_CP1_CI_AS
    • %SYSTEMDRIVE% formatted with the NTFS file system
    • SQL Server Full Text Search

Reporting Server

  • Access to reports provided via Operations Console. (Security integrated with OM roles.)
  • Reporting Server, is installed on a Reporting Services instance.
  • The minimum supported hardware configuration for the Reporting Server component is as follows:
    • 2.8GHz or faster x64 processor
    • 2GB of RAM or more
    • 20GB of available hard disk space
  • The software requirements for the Reporting Server component are as follows:
    • Windows Server 2008 R2 SP1
    • SQL Server Reporting Services 2008 SP1 or higher
    • SQL Server Reporting Services 2008 R2 or higher
    • .NET Framework 3.5 SP1
    • .NET Framework 4.0
    • At least 1024MB free hard disk space on %SYSTEMDRIVE% drive
    • SQL Collation: SQL_Latin1_General_CP1_CI_AS