Technology, especially the real time, are of great help if you are oceans apart and divided by time zone. I had an interesting talk with my buddy and SAP HANA expert from New Zealand this morning regarding data load in SAP HANA (Just to let you know, I am in Germany right now). I felt it might be useful to share and document the discussion for our own references in future 🙂 .
( I have discussed the topic of Data Load into SAP HANA in details, in my book title ‘Real time Analytics with SAP HANA‘ (Chapter 3: Different Ways of SAP HANA Data Load)).
Please check my book Here.
Backdrop of the call: With SP09 of SAP HANA, SAP has tried to make it easier and reduce the confusion over the topic of Data Load in SAP HANA. With SAP HANA Smart Data Integration Feature, you get one in all package(+ difference combinations ) of all the loading tool for loading data into Single HANA Instance. The intension was to reduce the confusion over whether to use SAP Landscape Transformation (SLT), Data Services (DS), Smart Data Access (SDA) or get a single UI that support all the available tool.
There are justified and valid use cases where Single tool makes more sense and should be preferred (we are not going to discusses that here, as this is more of conversation that I and George had this morning)
Extract from our discussion. In conversation with SAP HANA Expert and Solution Architect. I have removed the bullshit bingos that we talked: 😀
George – I think we no longer need SLT to replicate Data in Real-time in SAP HANA Side Car, as we have Smart Data Integrator (SDI).
Vinay – It depends J ( I learned the word from my Corporate Finance Professor). You will not need the advance features of Smart Data Integrator, if you are just doing 1:1 replication from Source to SAP HANA. Or let’s put it straight it would not be worth.
G – Can you re-iterate? What is Smart Data Integrator and SAP SLT in brief? I am confused now.
V – Let me tell you the major difference, that comes to my mind immediately, which I think might help you to differentiate:
Also Read: ‘SAP HANA from space level’
G – But, in my project my replication needs are mixed, I need to have support for
– Real time as well as batch
– Transform the data (for batch and some time for real time )
– We are also having mixed scenarios – cloud solution on-premise solution
I was looking forward for one UI that supports all, one connectivity that supports all my above needs. Should I not move to SDI completely and lay off my SLT and Data Services ?.
V– Again, it depends.
(disclaimer – below answer is comprehension of what I read in one of the discussion at SCN, earlier )
In a simple glance Data Services and the Smart Data Integration features sound similar things. But we will have to see the use cases.
Do you have all the instances/application running on SAP HANA? HANA solution requires HANA, so Data Services is still required for all use cases that are not using HANA or where you are using HANA only as database.
With SAP HANA the major focus is real-time. But with Data Services you can do Near real-time and batch processing. The HANA solution does support batch as well for the initial load, the primary focus was the question “When the source sends a change row, how to transform this row according to the initial load rules so the target data is correct“. In Data Services you have to build an initial load, you have to find out how to identify changes and build data flows that handle the various changes. The intention of the HANA solution is to do as much as possible automatically.
Because of the real time focus, the HANA solution does transactional consistent loading. One of the design differences with Data Services.
And the final difference, HANA requires access to remote data in various ways, not only batch and real time. It should support Smart data Access, Calc views etc.
So only if you use Data Services exclusively to load into HANA, only then you should consider the HANA SDI option. As we have overlap only in this scenario.
G – One of our sister concerns are moving to SAP HANA SPS10 for their reporting needs (transactional as well). They will have HANA as Platform, so should we recommend to get rid of DS?
V – For such scenarios, Yes. But as many experts say, get started on the HANA to gain experience. If you have Data Services already, do not exchange the technology right away. Wait for SAP to give us a migration path from the DS engine to the HANA engine.
We had to stop our discussion here as we were interrupted by something. Would post if G and I have some interesting talk again.
If you want to get such unconventional articles, practical tweaks and tricks straight to your inbox, please SUBSCRIBE. We respect your privacy and take protecting it seriously.
If you liked this post, please hit the share buttons at the left side of your screen. Please like us at facebook and encourage us.
Thank you very much for your time!!
Series on SAP HANA
to be updated..
(Image courtesy : https://blogs.saphana.com/wp-content/uploads/2014/03/sap-bw-7.4-with-in-memory-data-dabric.jpg)