Command Timeout Seconds

One of the most important workflows performed using the Data Warehouse module is the StandardDatasetMaintenance workflow. This is performed for each data set (alert, event, performance, state, and custom data sets like the Exchange 2010 management pack creates).
The StandardDatasetMaintenance workflow transforms the raw data from the Data Warehouse raw data set tables into daily and hourly data (called data aggregation) and stores it in the appropriate tables. This workflow is also responsible for grooming (deleting) the raw data after it is processed (aggregated). The setting that defines the timeout for this workflow is Command Timeout Seconds of type DWORD, and its default value (in seconds) is 300 (decimal). In large environments or environments where a large amount of data is collected for one or more data sets, the default timeout is usually not big enough, so in these cases, the recommended value is 1200 (decimal).

This registry setting helps with dataset maintenance as the default timeout of 10 minutes is often too short. Setting this to a longer value helps reduce the 31552 events you might see with standard database maintenance. This is a very common issue.

This policy create registry key: "HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse\" and REG_DWORD Decimal Value: "Command Timeout Seconds".
SCOM 2012 existing registry value: not preset (must create "Data Warehouse" key and value).
To delete REG_DWORD value from registry, disable this policy.

Default in code value = 300 seconds (5 minutes).
Minimum value (in this group policy template) = 300
Maximum value (in this group policy template) = 1800 seconds (30 minutes)
Recomended value for large environments: 900-1200 seconds (10-20 minutes)

Supported on: System Center 2012 Operations Manager

Registry PathSOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse\
Value NameCommand Timeout Seconds
Default Value
Min Value300
Max Value1800