SCOM Datawarehouse Alert.AlertStage Table Growing Very Large

Problem Noticed:

My DataWarehouse Was growing very large.

After setting the Grooming settings for the collected data, it still continued to grow very quickly.

Ran dwdatarp.exe against the database and found that my the Configuration Dataset was taking up the most space. (90%+) Found this on Kevin Holman's Blog

http://blogs.technet.com/b/kevinholman/archive/2010/01/05/understanding-and-modifying-data-warehouse-retention-and-grooming.aspx

Found that the reason for the configuration Dataset being so large was the Alert.AlertStage Table.

Immediate Fix:

The best immediate fix I've found so far is to truncate the Table (As Long as No data in there is needed, and in my case it isn't) This is done by running the following Command:TRUNCATE TABLE ALert.AlertStage

I found this fix reference in many different places, but this link provided the best explanation in my opinion.

http://bsuresh1.wordpress.com/2014/03/18/alert-data-is-not-being-inserted-into-scom-data-warehouse/

Root Cause:

I'm still trying to understand the Root cause as to why this is growing so large and so quickly.  (Any suggestions on items to check would be appreciated)

One Thread said they renamed the "Health Services State" folder on each of the Management servers and this corrected the issue, however, other than clearing out cached/old data and forcing SCOM to re-create the folder structure, I'm not sure what this really achieves.  I'm thinking the problem will return.

I will try it anyway to see what happens.

http://social.technet.microsoft.com/Forums/en-US/d2fad813-f68a-40af-bad0-01a9e24a6b4e/datawarehouse-alertalertstage-growing?forum=operationsmanagergeneral

Bobby Pendino