http://scn.sap.com/thread/3617189
How does HANA handle "Data Type" aka "Data Class" in the BW infoprovider database storage parameters? Does the data type/class have any relevance in HANA and the DMO tool?
In another SCN thread linked here, Marc Bernard said that since there are no tablespaces in HANA, the data class settings have no impact in HANA. However, he says that "only system copy tools still use the data classes.".
My question is whether the DMO tool that does the migration export/import is considered a 'system copy tool' and uses these data classes, and what are the implications?
We have used custom data types / classes in BW to segregate and manage separate Oracle tablespaces for each reporting area InfoProvider in BW. See the data type maintenance in BW at RSA1 > InfoProviders > Display > Extras > DB Performance > Maintain DB Storage parameters. The original purpose of maintaining separate tablespaces was to enable reorganization of tablespaces and reclaim space without locking ALL reporting area tables and impacting data loads. This doesn't seem necessary anymore since locally managed tablespaces were introduced, so we are trying to determine if we need to do anything with these custom data classes before migrating to HANA.
Relocating all the fact, dimension, MD, PSA, etc. tables back into the standard default data types would require a lot of effort, so our inclination is to leave the custom BW data types/classes as-is, and just use the default data types going forward. But, it's unclear how the existing custom data classes may be used in the migration with DMO. Are there any potential implications of these custom data classes in DMO and beyond?
Any advice and info is most appreciated!
Thanks,
Doug