Hi Sam,
Thanks for the insight. I understand MII on HANA can leverage the massive data storage capacity of HANA, but to leverage the performance improvement features provided by HANA ideally we should use the analytic and calculation views (code push-down) instead of writing complex application logic in the application layer i.e. BLS in this case. Infact from HANA development perspective it is not recommended to create the queries directly on the column tables, but instead use analytic and calculation views on which we can write the queries.
So now the issue is if we use MDO we can't easily develop the HANA views on it (as MDO names are cryptic in DB layer) and if we use HANA tables and views it'll be bypassing the content management and other features of MII. What you suggest in this scenario? Is there any enhancements being planned on MII for future releases to be more tightly coupled with the HANA platform and leverage the HANA features? If yes any timeline for that and what possibly we can expect going forward?
Also can you please clarify if the HANA database objects (tables and views) are accessible from MII SQL Query templates or do we need to use only oData services to call any query/views?
Thanks,
Dipankar