Concept card

Connections & Source Systems

As of 2026-07-24T14:00:00Z

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is Connections & Source Systems?

60% of post-go-live performance escalations trace back to a Connection wired without understanding the source system's pressure model — configuration is not a set-and-forget step.

What it is

A Connection in SAP Datasphere is the configured link between the tenant and an external system — bundling the credential, the network path, the protocol, and the access scope that together determine whether a source can be queried live, replicated in bulk, or both. It is a deceptively small piece of configuration that determines the performance ceiling of everything built on top of it.

Why it matters

Connection design is where a Datasphere project quietly decides whether its federation experience will feel instantaneous or will time out under real user load. Because the decision is made once, early, by whoever configures the source, and because its consequences only show up months later under production concurrency, connection design is one of the most under-scrutinized parts of a Datasphere build — and one of the most common root causes of post-go-live performance escalations.

How it works

Why it matters in practice

The wrong combination among credential, network path, capability flags, and schema cache is the root cause of most 'why is my federation slow' tickets.
SAP-native connections ship delivered metadata and CDS consumption no third-party connector matches — picking the wrong family throws that advantage away.
REST-based SaaS sources suit dimension-table replication but are painful for federation since their APIs weren't built for analytical push-down.

Key points

30+ connector types in 5 families: SAP-native, Cloud DWs, SaaS apps, Files+S3, JDBC/ODBC.
A Connection wraps four things: credential, network path, capability flags, schema cache.
Cloud Connector for SAP on-premise default; Private Link above 100 concurrent or 1 TB/day.
Replication needs CDC at source (S/4 native, SLT, ODP) — without it, 8-hour batch windows.
Service-account auth almost always (impersonation breaks DAC consistency).
Schema introspection cache stales daily by default; tighten on volatile sources or trigger from source release pipeline.
Credential rotation 90d / 30d — automate or it falls behind.
Federation cost = source CPU; 50 SAC users × 6 widgets × 200 ms = 1 vCPU steady source-side load.
Connections & Source Systems is mastered only when it changes a named buyer decision.
Start with the semantic contract and control model before demonstrating the tool.

Terms used on this page

Connection: Configured link between Datasphere and a source/target — credential + network + capability + schema cache.
Cloud Connector: SAP-shipped Java tunnel between on-premise systems and BTP. ~100 concurrent connections per instance.
Private Link: Cloud-native network peering (AWS PrivateLink, Azure Private Endpoint, GCP Private Service Connect) — higher throughput than Cloud Connector.
CDC (Change Data Capture): Source-side mechanism that streams committed changes (inserts/updates/deletes). Required for sub-hour replication latency.
ODP-CDS: ECC extraction protocol — Operational Data Provisioning over CDS views — the canonical CDC path from ECC to Datasphere.
SLT (System Landscape Transformation): SAP add-on for real-time table replication from any SAP/non-SAP source. Powers most ECC→Datasphere CDC.
Federation: Live SQL push-down to source — no copy, no latency, but every query consumes source CPU.
Schema introspection: Metadata discovery on a source — produces the catalogued table+column list the Modeler sees in the UI.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →