Hi ...You can consider these points.
1. Creating Aggregates with Calyear selection.. Like an aggregate with current 2 years data. This would be smaller than Cube .
2. While defining aggregates Calday should be a part of your aggr obviously. Check Charac in KF restriction and Charac on rows. You can leave charac in Free Charac pane from aggregate definition.
3. If you include let's say customer in aggregate definition, then there is no point keeping customer group outside.. Because customer grp in this case would not increase the number of records in aggregate.
4. You can have a separate cube for historical data. If you have query on MultiProvider you can provide a selection on 0INFOPROV to select current or historical cube.
5. You can go for DB partition.
6. Whatever you do , you would not get BWA like performance. Best performance you can get from creating a current and historical cube and put the current cube on BWA.. Here you can save some memory in BWA plus get excellent runtime.
Cheers
Anindya
