This blog would have better been named "Oracle legacy syntax not working on any other DBMS"...
To your points:
A) TRUNCATE: truncate table works for me in HANA: If you get an exception in ABAP for that, this should be further analysed - not just hidden in a CATCH section
B) INSERT /*+APPEND*/ works without any change of code. The hint is simply ignored by HANA.
NOLOGGING on the other hand is not supported on statement level (and should be used with GREAT care anyhow)
C) CREATE OR REPLACE VIEW is not available, correct. Also: it totally bypasses the ABAP DDIC management. That's not really nice for permanent views.
If the views are just temporary (like SAP BW creates temp. objects) then you might be better off with DROPPING anyhow.
D) Instead of DECODE, you might use MAP(). A more complex rewrite into CASE is not required most of the time.
Other than that... why is there a screenshot for the first section of this blog?
Couldn't you take a printout of the screen, create a copy on the xerox machine, fax it to the outlook server and attach it as a PDF file instead? 😉
Luckily you have only a few of these native SQL implementations with "third party" RDBMS vendors nowadays. Think about possible migration scenarios from HANA to any other RDBMS systems (e.g. MS-SQL, DB2 or whatever) in the future, when a lot of the processing / business logic is off-loaded to the HANA database layer .. that will be great fun 😛
However it seems like SAP is scared about IBM DB2 BLU technology ( 😉 ) nowadays and i am curious about the upcoming transparent "in-memory acceleration" by Oracle (maybe the SAP database licensing cost will be raised to 30 percent or so then) 😈
Spot on Stefan!
It will definitively become interesting to see how customer landscapes evolve over the next years.