Management Pack Audit - grooming data

%3CLINGO-SUB%20id%3D%22lingo-sub-2772850%22%20slang%3D%22en-US%22%3EManagement%20Pack%20Audit%20-%20grooming%20data%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2772850%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3ELast%20time%20I've%20checked%20my%20test%20SCOM%20environment%20and%20I%20noticed%20a%20huge%20size%20for%20DW%20database%2C%20specially%20One%20column%3A%26nbsp%3B%26nbsp%3BManagementPackChangeAudit%20-%20200%20GB.%20A%20lot%20of%20rows%20-%20many%20thousand%20and%20date%20last%20object%20much%20more%20than%20one%20year%20-%20405%20days!%20Is%20it%20possible%20to%20create%20rule%20and%20procedure%20in%20new%20UR%20where%20could%20determine%20time%20you%20want%20choose%20for%20grooming%20old%20data%3F%3C%2FP%3E%3CP%3ESecond%3A%3C%2FP%3E%3CP%3EBased%20on%20%22%3CSPAN%3EGrooming%20settings%20are%20tied%20with%20management%20pack%20grooming%20settings%20for%20data%20warehouse.%20This%20means%2C%20by%20default%2C%20three%20versions%20of%20management%20packs%20and%20400%20days%20old%20data%20will%20be%20shown%20in%20the%20reports.%20For%20example%3A%20whenever%20you%20make%20a%20change%20in%26nbsp%3B%3C%2FSPAN%3E%3CEM%3EMyCustomMP%3C%2FEM%3E%3CSPAN%3E%26nbsp%3Band%20save%20your%20changes%20in%20a%20new%20version%20as%20v1%2C%20v2%2C%20v3%2C%20v4%20over%20Seven%20days.%20Then%20by%20default%2C%20v1%20will%20be%20groomed%20and%20you%20will%20only%20see%20changes%20for%20v2%2C%20v3%20and%20v4.%20Besides%20this%2C%20any%20change%20which%20is%20400%20days%20old%20will%20be%20groomed%3C%2FSPAN%3E%22.%3C%2FP%3E%3CP%3EWe%20have%20a%20lot%20of%20automate%20tools%20and%20increase%20version%20of%20Management%20Pack%20is%20not%20good%20option%20always.%20Sometimes%20you%20don't%20want%20increase%20version%20of%20MP.%20So%20based%20on%20this%20grooming%20old%20data%20is%20not%20possible%2C%20because%20version%20of%20MP%20is%20still%20the%20same.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi All,

Last time I've checked my test SCOM environment and I noticed a huge size for DW database, specially One column:  ManagementPackChangeAudit - 200 GB. A lot of rows - many thousand and date last object much more than one year - 405 days! Is it possible to create rule and procedure in new UR where could determine time you want choose for grooming old data?

Second:

Based on "Grooming settings are tied with management pack grooming settings for data warehouse. This means, by default, three versions of management packs and 400 days old data will be shown in the reports. For example: whenever you make a change in MyCustomMP and save your changes in a new version as v1, v2, v3, v4 over Seven days. Then by default, v1 will be groomed and you will only see changes for v2, v3 and v4. Besides this, any change which is 400 days old will be groomed".

We have a lot of automate tools and increase version of Management Pack is not good option always. Sometimes you don't want increase version of MP. So based on this grooming old data is not possible, because version of MP is still the same. 

1 Reply

Above Problem is still fixing by grooming procedure. I changed interval in MaintenanceSetting table for ConfigGroomingFrequencyMinutes = 2 and Version to 1 MP. Grooming is running, but a lot of data's and this require a lot of time for finish. Root cause was regarding to Notifications Library MP. Version of MP was still the same... changes were added, frequently.