on 05-17-2006 11:23 PM
Hello Gurus,
I was recently asked how I would design an InfoCube for the user to see Historical and Transactional data in the same cube.
I am little confused about the answer since all the data in the cube becomes historical as soon as latest data (Transactional data) is loaded.
Thanks,
-BC
HI Belly,
Welcome aboard!!
Historical data and transactional data are usually kept seperate. We use cubes for historical data and ODS for transactional data. What best you can do is store the details in both and then join them in a multiprovider.
Regards
Sriram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi:
If you want to have both Historical & Transactional data in the same cube, make sure you use Cube Partitioning.
This only applies if the BW is installed on Oracle.
Ram Chamarthy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The design depends on how much data you are having. If you have lot of data its better to use them separately.
When you create a cube you load historical data from source systems through a full load and later you will be doing delta loads to process new records.
As for as the data is conccerned a cube can contain both historical and transaction data.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Belli
Welcome to SDN
There are different ways to do depends on your requirement the general way is create two different cubes one for History and other for current Transactional and club them in a multiprovider for reporting.
Hope this helps
Thnaks
Sat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.