Hi Diva,
1. What is the difference between ADSO and OpenODS? ADSO and openODS both support field based reporting and Infobject level reporting .What are the benefits of using and ADSO over an openODS for reporting?
Open ODS view is a virtual provider and ADSO is a info provider.
2. Can ADSO act as a virtual provider i.e can it report directly from an ECC source?
No. By using SLT you can report on a live data but can't be used as a virtual provider.
3. What are the partitioning options available in an ADSO?
check the option "Dynamic Range partitioning" feature for Advanced Data Store Objects. SPO is planned for future release.
As per SAP note 2044468 "Partitioning is only available for tables located in the column store. The row store doesn't support partitioning." Also recommends partitioning, if there is a risk to reach the 2 billion record limit.
4. Is there a possibility to write partitioned data to disks in ADSO to reduce memory?
A given database table is either memory-based (HANA column or row tables), or disk-based (extended table of dynamic tiering). It is not possible to create a single table that has partitions in memory and partitions in dynamic tiering. Extended tables cannot be partitioned. When a partitioned in-memory column table is converted to an extended table (ALTER TABLE … USING EXTENDED STORAGE), the partitioning specification is dropped and the extended table is created as a non-partitioned table that contains the contents of all partitions of the original table.
5. As far as I know the request handling technique is Different b/w aDSO and In-Memory Cube or In-Memory DSO. Also in-bound queue in aDSO can be kept in the WARM data.
Regards,
Shakthi Raj Natarajan.