We implemented a BAM solution using BizTalk Server 2013 and Standard SQL server 2012 that contained an aggregation. We set up a scheduled aggregation as described here.
In production if we open the BAM portal and expand the Aggregations we always only see the most recent days data.
In contrast the UAT environment if we look at the aggregations in the BAM portal we see several months of data.
![clip_image002[5]](http://markbrimble.wpengine.com/wp-content/uploads/2014/09/clip_image0025.jpg "clip_image002[5]")
WE could not find any difference between the database objects between UAT and Production i.e. the BAM_AN_All_GCTM and the SQL agent job that runs the package regularly. We have confirmed that all the data is present in the BAMPrimaryImport tables but the portal is not displaying all the data.
After many days trolling through the BAM database objects we could not find any difference between UAT and Production.
Finally we discovered a custom SQL agent job that our BI team had written which was truncating the cube on the Analysis server. See the BizTalk process Cube
The moral of the story don’t try to double guess the Microsoft team. BAM was fine but it was custom code letting us down.
