If you have log-shipped or moved your BAM databases to another environment, you might find that the legacy data in your non-rta view vanishes and only recent data is displayed.
This defeats the purpose of having scheduled aggregations to view data over months. However, there is a way to “reset” your cubes.
In the BAMPrimaryImport database, there is a table called ‘bam_Metadata_AnalysisTasks’. This table keeps track of range of records that the cube processed each time it ran. This range is also used to define the view ‘bam_<cubename>_CompletedInstancesWindow’ that is used to populated the staging tables for aggregation.
The trick is to delete all the records from this table in the BAMPrimaryImport database.
Delete from bam_Metadata_AnalysisTasks where CubeName=’<cubename>’
GO
Insert INTO bam_Metadata_AnalysisTasks(CubeName,MinRecordID,MaxRecordID,LastStartTime,LastEndTime)
VALUES (‘<cubename>’,NULL,NULL,NULL,NULL)
Note: Run the above queries for all the cubes in question. DO NOT RUN IN PROD BEFORE TESTING.
After executing the above command, run the corresponding BAM_AN_<cubename> package. After this has completed, browse to the BAM portal and you will see all historical data again.
Cheers.
0.000000
0.000000
Filed under: BAM, General | Tagged: Aggregation, BAM, Cube, Reset | Leave a comment »