Skip to Content
Technical Articles
Author's profile photo Feng Liu

Replicating Data from Oracle to HANA using SAP HANA Web IDE SDI

This blog is under construction

Assigned Tags

      10 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Werner Dähn
      Werner Dähn

      Nice work, Daniel! I would wish things would not have gotten so complicated. So many things to do, so many settings, so many dependencies...

      Author's profile photo Feng Liu
      Feng Liu
      Blog Post Author

      Hi Werner,

      I hope this can get things easier! SDI is more like tool for developers.

      Thanks,

      Daniel

       

      Author's profile photo Werner Dähn
      Werner Dähn

      That was not the intention when I designed it.

      Author's profile photo Feng Liu
      Feng Liu
      Blog Post Author

      I am adding this to my wish list 🙂

      Author's profile photo Yuriy Volosenko
      Yuriy Volosenko

      Few comments from my side.

      1. Indeed very complicated setup comparing to other solutions on the market.
      2. Performance is not production ready. It is not fast and scalable solution. We had significant performance issues with this setup.
      Author's profile photo Werner Dähn
      Werner Dähn

      The SDI development guideline said:

      • “No setting stored in the source because you might have two agents, all settings are stored in Hana and provided to the adapter at start”. All Transaction Log based adapters store their settings in the source.
      • "One agent serves multiple Hana instances". If S/4Hana, BW and the Data Lake all want to read from one Oracle system, you need to install the agent on that system three times. Architecture isolates the agent on session level. Every new session, regardless from where, is independent. Hence no problem to support that. (Latest JDBC proxy addition violates that agreement)
      • “Users are business users, hence make it simple”. Look at the settings in the datastores. Tons of options.
      • “Simple UIs”. Migration to XSA made all UIs worse. Lots of above complexity stems from XSA.
      • RepTask is not simple either. You want to replicate 1000 objects, hence select them and go. Instead you have to make settings on each and every replicated object. Could have been an advanced setting instead. And if you forgot one table, the entire reptask start from scratch with an initial load of all – there goes your weekend.

      The list goes on and on and on…

      I am using the SQL commands most of the time, if I use SDI.

      However what I prefer is Kafka: https://blogs.sap.com/2019/12/10/modern-sap-erp-data-integration-using-apache-kafka/

       

      Author's profile photo Feng Liu
      Feng Liu
      Blog Post Author

      We have Kafka setup but I haven't got chance to try. Definitely will do.

      Author's profile photo Feng Liu
      Feng Liu
      Blog Post Author

      Hi Yuriy,

      It is bit complicated to configure the solution compared to other vendors. But SDI is HANA centric so performance is not bad after we evaluated top vendors on the market also it includes transformation and SDQ.

      Thanks,

      Daniel

      Author's profile photo Henrique Pinto
      Henrique Pinto

      What happened to this blog?

      Author's profile photo Michael Liermann
      Michael Liermann

      Hello Feng Liu, could you please restore your blog post? Thx in advance!