Code pushdown for database other than HANA

[Former Member]

Hello All,

There is lot of buzz around code pushdown to HANA database to take maximum advantage of HANA capabilities. My question here is how effective is code pushdown if backend database is not HANA but any other traditional database?

Similarly for New Open SQL, are all the features equally optimized for all databases.

Thanks

Shibha Jain

[kesavadas_thekkillath]

Hi Shibha,

As you might be knowing that open sql is generic & database independent , is interpreted by data base interface( buffering & client handling ) and then the DDSL( database specific libraries ) which converts the open sql to respective db specific native sql . So, when using the new open sql for code push down( Code to Data ), it will run independently of the underlying database. I hope this clarifies your question.

Also, you can have a look in Core data services which provides advanced view definition capabilities. Its really cool working in that. CDS uses the ABAP dictionary system,database interface and support for all db platforms supported by ABAP stack. Also, the sql syntax used to create a CDS entity is different from the open sql we write in ABAP. Later, to consume the CDS entity in ABAP we use the open sql.

You can enrol into this open sap course ABAP Development for SAP HANA and get more insight about Code push down.

Kesav

[Former Member]

Thanks Kesav for your response.

However my question is more towards performance of SQLs for databases other than HANA.

We have all read about best practices to be used in select statements while working on HANA database. Do the same best practices apply when working on any database other than HANA?

Shibha

[kesavadas_thekkillath]

Hi Shibha,

Let it be any DB , in general , no changes are necessary if the SQL code follows the golden open sql rules. Classic performance recommendations are valid always. Regarding the best practices, most old guidelines remains valid, there are some guidelines which are valid only for HANA DB which cannot be applied to other DB specific coding( ex: non indexed fields in where clauses )

In HANA DB there are some HANA DB specific properties/features which can yield you better results than the other, in such cases we can revisit the code and do the HANA DB adaptive changes. For ex: Hints in SQL, some sql dialect related to other db might be used in native sql calls, direct access to clusters etc, these has to be corrected in HANA.