From an SAP HANA perspective, what are the differences between SAP HANA Smart Data Access (SDA) and SAP HANA Smart Data Integration (SDI)? There are 2 correct answers to this question.

Question

Options

• ASDI provides the feature of data transformation while SDA does NOT have this option.
• BSDI is not flexible regarding customer enhancements, while SDA provides an SDK for this
• CSDI leverages an adapter-based framework, while SDA is based on ODBC drivers.
• DSDI only connects to non-SAP sources, while SDA only connects to SAP sources.

• A
  77% (23)
• B
  10% (3)
• D
  13% (4)

Explanation

A and C are correct because they accurately capture two fundamental architectural and functional distinctions between the two technologies.

Why A is correct: SDI supports data transformation through its replication flowgraphs and task plans, enabling ETL-style processing as data moves into HANA. SDA is a federation/virtualization-only technology - it creates virtual tables pointing to remote sources but cannot transform data in transit; it simply passes queries through.

Why C is correct: SDI is built on an adapter-based framework (the Data Provisioning Agent with pluggable adapters for specific source systems), which enables richer capabilities like real-time replication. SDA, by contrast, relies on ODBC/JDBC drivers to connect to remote sources, making it simpler but less capable.

Why B is wrong: This is the reverse of reality. SDI is the one that provides an SDK for building custom adapters, making it highly extensible. SDA offers far less flexibility for customer enhancements.

Why D is wrong: Both SDA and SDI can connect to both SAP and non-SAP sources - neither is restricted to one ecosystem.

Memory tip: Think "SDI = Sophisticated Data Integration" - it does more (transforms, replicates, uses adapters, has an SDK), while SDA = Simple Data Access - it just federates/virtualizes using drivers, no transformation, no replication.

No community discussion yet for this question.