I have been noticing that my DW has been growing in size, more and more. Today I took a look: Dataset name Aggregation name Max Age Current Size, Kb ------------------------------ -------------------- ------- -------------------- Alert data set Raw data 365 117,344 ( 0%) Client Monitoring data set Raw data 30 0 ( 0%) Client Monitoring data set Daily aggregations 365 32 ( 0%) Configuration dataset Raw data 400 1,045,048 ( 2%) Event data set Raw data 100 2,669,736 ( 6%) Performance data set Raw data 180 1,246,000 ( 3%) Performance data set Hourly aggregations 60 20,403,184 ( 46%) Performance data set Daily aggregations 180 1,152,096 ( 3%) State data set Raw data 180 706,896 ( 2%) State data set Hourly aggregations 60 15,765,728 ( 35%) State data set Daily aggregations 365 1,381,128 ( 3%) Then, I noticed that I have really old perf.Hourly history in my DB (over 400 days) via one of the queries I found online. Then I tried running the stored procedure people mention: Exec standarddatasetgroom" with all the DataSetIDs I got from the StandardDatasetAggregation table in the OperationsManagerDW DB. They all ran in under a second, and my database is still enormous. I don't think grooming is happening at all, manually or automatically. What should I do? Thanks, Reuv

You can use dwdatarp.exe to change the grooming of the datawarehouse.It is available for download HERE . Kevin Hollman also made a blog article about it, where he explains how to use this tool: Understanding and modifying Data Warehouse retention and groomingCertifications: MCSA 2003|MCSE 2003|MCTS(4*)| MCTIP:SA

You can use dwdatarp.exe to change the grooming of the datawarehouse.It is available for download HERE . Kevin Holman also made a blog article about it, where he explains how to use this tool: Understanding and modifying Data Warehouse retention and grooming Certifications: MCSA 2003|MCSE 2003|MCTS(4*)| MCTIP:SA

The output generated above was using that tool, and I did change the threshholds. My point was that in spite of the configuration change, which before hand was already set to 360 and I lowered it to 180, it is still not deleting stale data.

The data warehouse DB is fully self maintaining. By the way how big is your datawarehouse and how many agents you have in total? What does this query gives you: select ds.datasetDefaultName AS 'Dataset Name', sda.AggregationTypeId AS 'Agg Type 0=raw, 20=Hourly, 30=Daily', sda.MaxDataAgeDays AS 'Retention Time in Days' from dataset ds, StandardDatasetAggregation sda WHERE ds.datasetid = sda.datasetid ORDER by ds.datasetDefaultName Certifications: MCSA 2003|MCSE 2003|MCTS(4*)| MCTIP:SA

This explains why you might find older data than your grooming settings, ESPECIALLY in very small databases like yours: http://nocentdocent.wordpress.com/2009/02/18/scom-data-warehouse-grooming/ Kevin Holman