on 08-13-2015 10:39 AM
In classical BW environments, lots of InfoCubes are created with the sole purpose of performance, and are simply a 1:1 copy of the data in the DSO layer underneath it. So, Now in BW 7.4, by making a few minor adjustments to the DSO, and redirecting your Multi Provider (or Query) to the DSO instead of the InfoCube, can you decommission the InfoCube completely ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Michael,
We have evolved from SAP BI 7.0 are currently running BW 7.4. So, we are looking to
leverage the power of HANA DB and in this process we are trying to reduce the data footprint
in our current EDW layer to start with... and I'm trying to understand the options we have
to reduce the data footprint.
Regards,
Ashwin
Hi,
If you really want to lower the data footprint check out Open ODS. Open ODS View - Using the SAP HANA Database - SAP Library
Regards,
Michael Devine
Hi Michael,
Could you please share your thoughts on the best way to handle year specific cubes in BW 7.4? We have around 4 Info cubes (year specific) based on a single DSO and we want to leverage new modeling techniques provided in BW 7.4
Current State :
Info Cube 2
Info Cube 3
Info Cube 4
My Options are:
Advanced DSO 2
2. Multi Provider <-- Virtual Provider <-- Cal View 1 <-- DSO (main source) <--Extractor
Cal View 2
Cal View 3
Cal View 4
Kind Regards,
Ashwin
Why not just report directly off of the DSO? Extractor->DSO->Query. Multiprovider can go away since you no longer need to union the data (should be using composite providers anyhow). Depending on your requirements calculation views may not be necessary unless you need to bring in non-BW data. A lot of the complex calculations (including exception aggregation) are already processed at the HANA DB.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.