How will i knopw whether SCOM DB Grooming ran successfully aopart from looking into the ManintenanceSetting Db table // I read there is a a SP that runs every night p_Partitioningandgrooming , but i do not see any SQL Jobs for it.. What should be the name of the job that i should look for .. Also Need to Know how data is transferred from Opsmgrdb to DW

Found this: http://blogs.msdn.com/b/steverac/archive/2007/12/13/scom-2007-operational-and-datawarehouse-grooming.aspx Grooming happens through SCOM Rules.. No SQL Jobs I found the two DW tables for grooming and retention dbo .MaintenanceSetting , dbo .StandardDatasetAggregation But i am still curious to know how data moves between DB and DW..Who writes which data.. How would i know for how much time i will have a data related to an agent (I mean the duaration for which i can pull data using reports) Also am i correect if i believe that anyreport we run in SCOM , Pulls the data from DW and none use the DB Also whhat is Aggregation in simple terms

it doesnt write from the db to the dw. data will be written to either one of them or both by a management server. E.g. most perf data is written to both simultaneously aggregation is just how it will be stored so you have it available but doesnt consume too much space. Raw perf data in the dw is 2 weeks available by default (i think), but the hourly average (the aggregation) will be kept longer.Rob Korving http://jama00.wordpress.com/

I beleive that one of the last updates to the OM management pack added grooming monitoring. Check out the guide doc for the OM MP on the catalog.Microsoft Corporation

You can find more information about determining whether grooming is working here: http://blogs.technet.com/b/jonathanalmquist/archive/2009/12/22/monitor-the-operations-database-grooming-procedure-v2.aspx And Dan is correct - Monitoring the operational database grooming procedure is now included in the SCOM management pack since version 6.1.7672.0HTH, Jonathan Almquist - MSFT

it doesnt write from the db to the dw. data will be written to either one of them or both by a management server. E.g. most perf data is written to both simultaneously aggregation is just how it will be stored so you have it available but doesnt consume too much space. Raw perf data in the dw is 2 weeks available by default (i think), but the hourly average (the aggregation) will be kept longer. Rob Korving http://jama00.wordpress.com/ Just to be more clear about this, some data items are written to both databases at the same time, while others are synced over. Discovery Data (Instances) and Alerts are sync'd from the database to the data warehouse. Events, Performance data, State Changes are written to both databases at once. Michael Pearson OpsMgr Performance Test Team http://blogs.technet.com/michaelpearson/ This posting is provided "AS IS" with no warranties, and confers no rights. Use of attachments are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

Thank you All, I found this info useful as well. http://blogs.technet.com/b/momteam/archive/2007/10/30/event-alerts-perf-data-flow-in-opsmgr-2007.aspx