Symptom
You carry out a database migration of your BW 7.30 system to an SAP
HANA database (DB). You want to convert your InfoCubes and DataStore
objects to SAP HANA DB-optimized objects; however, some objects are used
in 3.x data flows. DataStore objects that are the source of a 3.x
update rule cannot be converted to SAP HANA-optimized DataStore objects.
Other Terms
ODSO, CUBE 3.x, data flow, conversion, migration, SAP HANA DB, HANA, SAP HANA-optimized
Reason and Prerequisites
DataStore objects are used in 3.x data flows in a BW system on an SAP HANA database.
Solution
A migration to an SAP HANA database is possible independently from
3.x data flows. After the migration, 3.x data flows are fully
executable; however, so that the performance advantages of the SAP HANA
DB can be fully utilized, we recommend that you convert all InfoCubes to
SAP HANA-optimized InfoCubes. In addition, we highly recommend that you
migrate all 3.x data flows to 7.x data flows because enhancements
always optimize regarding 7.x data flows. InfoCubes can be converted to
SAP HANA-optimized InfoCubes without restrictions.
For standard DataStore objects, the activation process on the SAP HANA DB is significantly improved in future Support Packages. A conversion to an SAP HANA-optimized object is an advantage only if an accelerated activation is definitely required already at this point in time. Otherwise, the effort required for the conversion and the subsequent restrictions regarding 3.x data flows outweigh the advantages. For DataStore objects, it is absolutely necessary that no update rules exist that use the DataStore object as a source. A conversion is not supported in such a case because there is no persistent change log for SAP HANA-optimized DataStore objects. In 3.x data flows, additional write accesses to the change log take place that would not be possible in this case. As mentioned above, an optimization regarding the SAP HANA DB will also be available for standard DataStore objects; this means that it is not absolutely necessary too convert from 3.x data flows to be able to use the advantages of the SAP HANA DB.
Additional information is available at: http://www.saphana.com/docs/DOC-3129
For more information about restrictions for the conversion of DataStore objects, refer to SAP Note 1665322.
In addition, refer to "Using the SAP HANA Database" in the BW 7.30 documentation under:
http://help.sap.com/saphelp_nw73/helpdata/en/af/81f38183cf46b9b919f82d7bb7ec47/frameset.htm
For standard DataStore objects, the activation process on the SAP HANA DB is significantly improved in future Support Packages. A conversion to an SAP HANA-optimized object is an advantage only if an accelerated activation is definitely required already at this point in time. Otherwise, the effort required for the conversion and the subsequent restrictions regarding 3.x data flows outweigh the advantages. For DataStore objects, it is absolutely necessary that no update rules exist that use the DataStore object as a source. A conversion is not supported in such a case because there is no persistent change log for SAP HANA-optimized DataStore objects. In 3.x data flows, additional write accesses to the change log take place that would not be possible in this case. As mentioned above, an optimization regarding the SAP HANA DB will also be available for standard DataStore objects; this means that it is not absolutely necessary too convert from 3.x data flows to be able to use the advantages of the SAP HANA DB.
Additional information is available at: http://www.saphana.com/docs/DOC-3129
For more information about restrictions for the conversion of DataStore objects, refer to SAP Note 1665322.
In addition, refer to "Using the SAP HANA Database" in the BW 7.30 documentation under:
http://help.sap.com/saphelp_nw73/helpdata/en/af/81f38183cf46b9b919f82d7bb7ec47/frameset.htm
Header Data
| Released On | 04.03.2013 15:34:34 | ||
| Release Status | Released for Customer | ||
| Component | BW-WHM-DBA Data Basis | ||
| Other Components |
| ||
| Priority | Recommendations / Additional Info | ||
| Category | Consulting |
No comments:
Post a Comment