Skip to main content

18.5 Open SQL & External Writes

1. What Open SQL provides​

SAP Datasphere spaces can expose Open SQL schemas that external tools can access using supported database connectivity.

This enables:

  • ETL tools,
  • custom applications,
  • partner platforms,
  • scripts,
  • integration services

to write data into Datasphere.

2. Pattern​

External platform
       |
   JDBC / ODBC
       |
database user
       |
Open SQL schema
       |
Datasphere table
       |
semantic model

3. Security​

Treat the database user as a production integration identity.

Control:

  • credential lifecycle,
  • privileges,
  • network restrictions,
  • ownership,
  • rotation,
  • monitoring,
  • separation of duties.

4. Push versus pull​

Push is useful when the external platform already owns extraction.

Pull is preferable when Datasphere should own acquisition and scheduling.

The choice should follow ownership, not convenience.

5. Operational controls​

Define:

  • batch identifier,
  • source timestamp,
  • load timestamp,
  • record count,
  • retry behavior,
  • duplicate handling,
  • reconciliation.

6. Application integration​

For application-generated events, consider whether a data-ingestion platform or event architecture is more appropriate than directly writing every event into an analytical schema.

Exercise​

An external Python service generates 50 million events daily.

Design an ingestion contract including:

  • batch identity,
  • idempotency,
  • error handling,
  • schema evolution,
  • security,
  • reconciliation.