Connectors Azure Synapse Analytics

Azure Synapse Analytics data integration with Lima, in both directions.

Azure Synapse Analytics combines a dedicated SQL pool with Spark pools and serverless SQL over Data Lake Storage. Lima lands Parquet in ADLS Gen2, loads the dedicated pool with COPY INTO, applies changes through staging tables and, where the estate prefers it, writes Delta tables read by serverless SQL.

SOURCESSAP ECC · S/4HANAreleased interfacesOracle EBS · Fusion · JDEdatabase reads · APIsDatabases, files, streamsJDBC · SFTP · KafkaLIMA BACKBONEExtractfull, incremental, change captureChecktypes · keys · counts · totalsLoadParquet to ADLS, COPY INTO staging, appl…TARGETAzure Synapse AnalyticsDedicated SQL pool schemas with hash dis…
How Azure Synapse Analytics fits the six Backbone steps. It is a source and a target: data comes out through the methods below, and results go back in with confirmation.
3
ways to read or write it
this connector
3
patterns supported
this connector
3
ways to run: SaaS, private cloud, on-premise
product
22 days
from contract to production
showcase estate
How Lima reads and writes Azure Synapse Analytics

Method by method.

Each method has a job. The first load uses the bulk method; the daily run uses the incremental or change-capture method; write-back uses the interface the system itself uses.

MethodWhat it doesWhen it is used
COPY INTO from ADLSBulk loads Parquet into the dedicated pool.First loads.
Staging + applyApplies changes by key.Deltas.
Delta on ADLSWrites Delta for Spark and serverless SQL.Lake-first estates.
What it covers

Objects and patterns.

The objects are the tables, views or records Lima reaches through the methods above. The patterns say how a copy is made and kept current.

ObjectPlain meaning
raw schemaas arrived
conformed schemacurrent by key
historyevery version
PatternSupported
Full loadYes
IncrementalYes
Change captureapplied through staging
Streaming—
Write-back—
What Azure Synapse Analytics expects

The landing model, and the hardest part.

ModelDedicated SQL pool schemas with hash distribution on the source keys; or Delta tables on ADLS.LoadParquet to ADLS, COPY INTO staging, apply by key; counts and control totals per table.BackResults can be written back to the ERP by Lima, confirmed per write.
The hardest part, in one sentence

Choosing distribution keys so joins across SAP tables stay local.

Before you start

Prerequisites, then four steps.

The prerequisites are what the team that runs Azure Synapse Analytics grants. The four steps are the same for every connector.

  • A service principal with storage and SQL permissions
  • A dedicated pool sized for the loads
  • Resource class for load users
Register the connectionEndpoint, credentials from the vault, and the method. The connection is tested and a failed test names the cause.
Choose the objects and the patternPick tables or objects from the discovered schema, and the pattern: full, incremental, change capture or streaming.
Run the first load with checks onEvery row is valid or becomes an exception with an owner. The run ends with a count and a control total per table.
Schedule it on the business calendarA run window with a deadline; pause, resume and replay if a check trips; the report after every run.
What happens to a bad record

Incoming data = valid records + exception records. A row that fails a check is kept, routed to the person who owns it with a deadline, and replayed once fixed. The load carries on with the valid rows and the report says exactly what was held back. How exceptions work →

Pair pages

Azure Synapse Analytics in a source-to-target path.

Each pair page covers one path end to end: objects out, model in, checks, cadence and the offer.

/connectors/sap-ecc-to-azure-synapse

SAP ECC to Azure Synapse Analytics

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/sap-s4hana-to-azure-synapse

SAP S/4HANA to Azure Synapse Analytics

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/oracle-ebs-to-azure-synapse

Oracle E-Business Suite to Azure Synapse Analytics

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/oracle-fusion-cloud-erp-to-azure-synapse

Oracle Fusion Cloud ERP to Azure Synapse Analytics

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/oracle-jd-edwards-to-azure-synapse

Oracle JD Edwards EnterpriseOne to Azure Synapse Analytics

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/peoplesoft-to-azure-synapse

Oracle PeopleSoft to Azure Synapse Analytics

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/microsoft-dynamics-365-to-azure-synapse

Microsoft Dynamics 365 Finance and Supply Chain to Azure Synapse Analytics

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/infor-ln-m3-to-azure-synapse

Infor LN and M3 to Azure Synapse Analytics

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/netsuite-to-azure-synapse

Oracle NetSuite to Azure Synapse Analytics

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/sap-bw-to-azure-synapse

SAP BW and BW/4HANA to Azure Synapse Analytics

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
Terms on this page

Plain meanings.

ConnectorA packaged way to read or write one kind of system, with its authentication, methods and prerequisites described.
Full, incremental, change capture, streamingFour ways to make and keep a copy: read everything; read what changed since last time; read changes from a log as they happen; consume events in small batches.
Write-backWriting a result into the system that owns it through its released interface; the system's response is the confirmation.
Control totalThe sum of a key amount column compared between source and target, along with the row count, at the end of a run.
Exception recordA row that failed a check: kept, routed to an owner, replayed once fixed.
Questions

Asked about this connector.

Does Lima install anything in Azure Synapse Analytics?

Lima connects from outside through the interfaces listed above with credentials your administrators grant. Where a vendor requires its own agent or add-on for a method, the prerequisites say so.

How is load on Azure Synapse Analytics kept in check?

Parallel reads are capped and the cap is agreed with the team that runs the system. Large reads run inside an agreed run window. Change capture keeps the daily volume small.

What do we see when a run finishes?

A report per run: rows in, rows out, control totals and variance per table, the exceptions held back and who owns them, and whether the deadline was met.

Can we start small?

Yes. Most estates start with one source, one target and one dataset, then add tables and patterns on the same connection.

Try Azure Synapse Analytics on your own estate.

A trial connects this system, runs a first load and ends with a reconciliation report. Your administrators see the prerequisites before anything is installed.