Professional Documents
Culture Documents
The first and most important point to consider here is the question itself: How to get data into Hana. If Hana is
just one of many sources and targets or there is no Hana in the picture at all, then the standalone products do
make more sense. Or to argue into the reverse direction, there are so many different options because of the
non-Hana scenarios. Okay, it would be odd if the standalone solutions can load everything but Hana, hence
they have that capability as well which creates that confusion.
Example: My task is to integrate various system, the sources are an SAP ERP system, 5 Oracle databases,
flat files of various formats, SQL Server,... and to load that into Teradata, Oracle and BW on Hana.
So Hana plays no or a little role in it, sounds like a perfect SAP Data Services scenario. Many sources, many
targets and Data Services in the middle.
SAP HANA Developer Center: The various Data Provisioning Options for Hana
In case the source data should be just made available and not copied - the federated/virtual data model use
case - SDA would need to be configured as well.
So at the end, for an e.g. SQL Server database as source, three products are needed. All with their own install,
with their own connector to the source, totally different look and feel and different capabilities.
Customer wants to perform Data Services like transformations in Realtime? Not possible.
Customer wants to perform Data Services like transformations in a CalcView for virtual data models?
Not possible.
Customer wants to tryout one style, e.g. a virtual data model and then switch to batch data integration
for performance reasons and then to realtime data integration for accuracy? No way.
Customer wants to administer, maintain and monitor all from Hana? No chance.
Customer wants to read from something less common, say MySQL? Only Data Services has that
possibility.
For these reasons the Hana EIM Option Smart Data Integration was developed. Take the best concepts of
all the products, merge those with existing Hana features and quickly you can develop the most powerful and
easy to use product from ground up. Yes, SDI does not reuse any code from the old products.
see Playing Lego with SDI
Essentially, SDI is an extension of SDA which enhances it by
Adapters
Running outside of the Hana kernel - hence are not a stability threat for Hana
Provide an Adapter SDK to write new adapters easily - every customer has a few common
sources SDI provides adapters for plus one exceptional. They can write a new adapter for that
within hours/days.
Support onpremise and cloud deployments - a Hana cloud can read onpremise data as if it was
local
Realtime Push
Adapters do support select and insert/update/delete but also a realtime push of change data
Transformations
All Data Services and Hana transformations are available in Hana natively
UIs
A Data Services like UI for the assembly of dataflows and the configuration of the individual
transforms
Supports batch reading, realtime transformations and virtual data models
Hana Cockpit for monitoring and administration
SAP HANA Developer Center: The various Data Provisioning Options for Hana
It does not make sense to have one adapter supporting all options or one adapter per realtime method. Hence
the SDI OracleLogReader adapter is using the LogMiner technology for realtime plus the JDBC driver for
normal reads.
Later we might add more adapters to support other realtime APIs as well, in case these are preferred by a
customer.
SAP ERP is another example where multiple technologies could be used. There is certainly no JDBC driver for
SAP ERP, so even reading tables is a challenge already.
ABAP Adapter: Reads SAP tables via ABAP, also can read from Extractors and call BAPIs.
ECCAdapter: This is a variant of a database adapter, so it does use the database transaction log to
get the changes for realtime. But returns the data in the ABAP datatypes and deals with pool/cluster
tables correctly.
SLT Adapter?? This one is missing as of today. Would totally make sense to utilize SLT and its
trigger based realtime approach to get the changes from ABAP tables. see ideaplace to vote up if you
agree.
Also keep in mind, there are certain features missing as of today (SPS11), like Workflows. This is high on the
priority list. The product was first delivered with Hana SPS09 which is relatively young compared to all others.
But again, SDI is the supposed optimal solution only because we have reduced the question to "loading into
Hana".
SAP HANA Developer Center: The various Data Provisioning Options for Hana
There are more than enough use cases, even in the Hana world where other tools have the edge.
SAP HANA Developer Center: The various Data Provisioning Options for Hana
For ABAP savvy users this is certainly the preferred option still. From a technical point of view 90% of the logic
of SLT is what you would call an adapter in SDI. That is the reason why adding an SLT adapter to SDI would
make so much sense.
SAP HANA Developer Center: The various Data Provisioning Options for Hana
SAP BW
With SAP BW on Hana the user is in a very comfortable position. For SAP extractors for example SAP BW has
native support, why go another route? Hana data can be read as well. And for none-Hana data BW is using the
Hana virtual tables, the SDI solution hence.
Therefore BW should not be considered an alternative but instead BW can utilize all other loading options to
take advantage of those.
Hana SDA
This feature enables the use of virtual tables in Hana. These are Hana objects that point to an external system
to blend in the remote data in Hana. For example a SQL Server table CUSTOMER_MASTER can be blended
SAP HANA Developer Center: The various Data Provisioning Options for Hana
in to Hana as virtual table V_CUSTOMER_MASTER. This virtual table is nothing else than a pointer to the
remote table. So it does not store any data on the Hana side, all queries are forwarded to the remote system
and the data retrieved.
SDA provides a set of adapters, all running in the Hana IndexServer and do use ODBC drivers. Nowadays the
SDI provided adapters are used instead.
Hana SDI
This solution is a natural part of Hana and extends Hana SDA. Therefore all Hana products and applications
can take full advantage of its capabilities just like SDI does utilize other Hana features.
SAP HANA Developer Center: The various Data Provisioning Options for Hana
Hana SDS
Hana Smart Data Streaming again does actually compare to the other Data Provisioning options. Although
it has adapters as well, its main goal is to aggregate the incoming stream of data, mostly by time slices. A
good example is the streaming of WebLog changes. Instead of storing the billions and billions of raw weblog
information in Hana, it might make more sense to extract key information from the raw data and store this
information instead. How many users have viewed a web page within 10 minutes intervals?
Therefore the SDS provided adapters are more focused on these kinds of source which produce millions of
rows per second and not database sources. It does support reading from databases as well but just to lookup
master data, not to subscribe to database changes.
SAP HANA Developer Center: The various Data Provisioning Options for Hana
chandan praharaj
Jul 27, 2016 3:54 AM
Hi Werner,
The document is quite informative, still I have 2 questions, please help me resolve this.
1. SRS and SAP DS both are from many to many system, so can we use them alternately, or do they have
separate use cases.
2. You have covered one point regarding SLT adapters,
so if SLT Adapters will be there in future, all the real time replication from ABAP based system can be made
real time with SDI, right? So no additional licencing for SLT?
Werner Daehn in response to ram nath on page 9
Jul 21, 2016 10:09 PM
The task supports everything SQL supports and SQL has a CASE-WHEN expression. Use that as mapping
expression.
link
ram nath
Jul 21, 2016 9:33 PM
Hi Werner,
SAP HANA Developer Center: The various Data Provisioning Options for Hana
IS the HANA SDI has option to split the column based on the two values is such kind of functionality is
available similar to Data services.I like to know the options for splitting into two columns based on the values.
Is it possible to write ifthenelse,Case statement functions in edit expression level.
Thanks,
Ram
Werner Daehn in response to Roberto Falk on page 10
Jul 5, 2016 6:57 PM
SDI: yes, see Ben Hofman's blog post
SDA Adapters: no, would require installation of ODBC drivers
SDA with SDI Adapters: yes
SDS: yes
SLT: depends. Needs an ABAP server somewhere and Hana Cloud Connector for the network
access.
PI: does not apply, no SOA services. If you write those, then yes.
Data Services: No, but there is HCI-DS, a small scale version of DS for Hana Cloud Integration. Its
backend will be moved to SDI sooner or later, though.
SRS: you install SRS onpremise and using Hana Cloud Connector open up the network? Should
work.
SAP BW: does not apply
SAP HANA Developer Center: The various Data Provisioning Options for Hana