Analytics Legends The knowledge platform for SAP Analytics
Academy module

Remote Tables & Federation

Federate versus materialize decision flow for Datasphere remote tables — architecture diagram for Remote Tables & Federation, Analytics Legends Academy module M007

As of 2026-08-16

Edited by , sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

Federation = live SQL to remote source, no copy in DSP. Senior rule: < 5 % of volume, never dashboard sources. Wins on ad-hoc analyst queries, residency-strict reference data. Loses on joins > 100k rows, > 2 consumers/h, dashboards. Document federate-vs-materialize decision per table in ADR; reassess quarterly.

What you will learn

  • Understand the core concepts behind remote tables & federation
  • Apply Federation in a typical SAP analytics engagement
  • Recognize the 3-5 common mistakes and how to avoid them
  • Position this skill in your personal brand and rate conversation

Module overview

Federation in Datasphere = live SQL against an external system without copying data into DSP. The senior rule: federation is a tool of last resort, used for < 5 % of volume, never for dashboard sources. Wrong use of federation is the #2 cause of "DSP performance is bad" tickets (after wrong partition count in Replication Flow).

When federation wins. Ad-hoc analyst queries against a small remote table that changes too rapidly to replicate. One-time data exploration before deciding what to ingest. Reference data with strict residency requirements (data must never leave source jurisdiction).

When federation loses (almost everywhere else). Dashboard sources (5-30s latency unacceptable). Joins above 100k rows (network round-trip explodes runtime). Production reporting (depends on remote system availability). Data with > 2 consumers per hour (cumulative load > replication cost).

The technical reality. Remote tables in DSP point at on-prem HANA via Smart Data Access (SDA) or at cloud sources via a connection. Each query traverses the Cloud Connector, hits the source, returns rows. Cardinality of 100k rows = 5-30s round-trip; cardinality of 10M rows = unusable.

Prerequisites

  • Review core concepts first: C008, C006, C004

Outcomes

  • Understand the core concepts behind remote tables & federation
  • Apply Federation in a typical SAP analytics engagement
  • Explain the core architecture and decision points for Remote Tables & Federation
  • Apply a repeatable implementation pattern in a 15-minute lab format

Full module available to members. The full module adds: the decision framework · the end-to-end scenario walkthrough · the KPI scorecard · the anti-patterns · the code blocks · the knowledge check · the diagrams.

Open in the app →

Next in this track