Two-way sync
Changes in Azure Synapse Analytics or IBM AS/400 instantly reflect in both systems. No stale data, no manual imports.
Keep Azure Synapse Analytics and IBM AS/400 in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Operational databases and analytical warehouses want the same data at different moments. Analysts want IBM AS/400's rows in Azure Synapse Analytics, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in IBM AS/400 where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in IBM AS/400 sync into Azure Synapse Analytics in real time, and result tables in Azure Synapse Analytics sync back into IBM AS/400, with schema and type mapping between the two systems handled for you.
Rows from IBM AS/400 land in Azure Synapse Analytics as they change, replacing hand-built CDC and batch extract jobs.
Aggregates or model outputs computed in Azure Synapse Analytics sync into IBM AS/400, where whatever reads from that database gets them without querying the warehouse.
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Azure Synapse Analytics objects | IBM AS/400 objects | How this pairing syncs | |
|---|---|---|---|
| Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. | Rows / records The unit of read and write, accessed via SQL or record-level access. | Tables (dedicated SQL pool) is specific to Azure Synapse Analytics and Rows / records to IBM AS/400 — each maps to any object or custom field on the other side. | |
| External tables Tables over files in the data lake, queried through serverless SQL and often read-only in syncs. | Journals and journal receivers The change log that enables log-based CDC on journaled files. | External tables is specific to Azure Synapse Analytics and Journals and journal receivers to IBM AS/400 — each maps to any object or custom field on the other side. | |
| Views Curated projections used when downstream tools should not read base tables directly. | Data queues Program-to-program messaging objects sometimes used to hand events off to integrations. | Views is specific to Azure Synapse Analytics and Data queues to IBM AS/400 — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that separate staging, integration, and presentation layers. | Libraries The schema-equivalent containers that scope which files a sync reads. | Schemas is specific to Azure Synapse Analytics and Libraries to IBM AS/400 — each maps to any object or custom field on the other side. | |
| Materialized views Precomputed aggregates that speed reads of frequently synced result sets. | Physical files (tables) The Db2 for i tables mapped directly to sync targets. | Materialized views is specific to Azure Synapse Analytics and Physical files (tables) to IBM AS/400 — each maps to any object or custom field on the other side. | |
| SQL pools Dedicated or serverless compute contexts that determine how and where queries run. | Logical files (views) Indexed or filtered views over physical files, usable as read sources. | SQL pools is specific to Azure Synapse Analytics and Logical files (views) to IBM AS/400 — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionStacksync polls Azure Synapse Analytics for changes on an incremental schedule, reading only records changed since the previous pass. Polling on watermark columns.
DeliveryEach detected change is applied to IBM AS/400 as a row-level write, with types converted between the two schemas.
DetectionChanges in IBM AS/400 are captured at the source via change data capture — no polling loop against its API. Journal-based CDC by reading journal receivers on journaled files.
DeliveryEach detected change is applied to Azure Synapse Analytics as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Synapse Analytics–IBM AS/400 connection.
Changes in Azure Synapse Analytics or IBM AS/400 instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Azure Synapse Analytics or IBM AS/400 data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Azure Synapse Analytics or IBM AS/400 record.
Track your Azure Synapse Analytics ⇄ IBM AS/400 sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure Synapse Analytics and IBM AS/400.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Azure Synapse Analytics and IBM AS/400 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Azure Synapse Analytics and IBM AS/400 objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Azure Synapse Analytics and IBM AS/400: authenticate both systems, choose the objects to sync (such as Azure Synapse Analytics's Tables (dedicated SQL pool) and External tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Azure Synapse Analytics side: SQL pools, Tables (dedicated SQL pool), External tables, Views, plus custom fields where Azure Synapse Analytics exposes them. On the IBM AS/400 side: Journals and journal receivers, Data queues, Libraries, Physical files (tables). Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Azure Synapse Analytics and IBM AS/400: Operational data in the warehouse, minus the pipeline; Serve warehouse results at database speed; Fresh analytics without loading windows. Rows from IBM AS/400 land in Azure Synapse Analytics as they change, replacing hand-built CDC and batch extract jobs.
Azure Synapse Analytics: SQL wire protocol (TDS) with T-SQL for SQL pools; additional Spark and pipeline surfaces exist but syncs use the SQL endpoint. Authentication: SQL authentication or Microsoft Entra ID. IBM AS/400: SQL over JDBC/ODBC to Db2 for i (for example the JTOpen/jt400 driver), alongside native record-level access. Authentication: IBM i user profile credentials (database credentials). Stacksync manages authentication, retries, and rate limits on both sides.
Azure Synapse Analytics: The serverless SQL pool queries files in the data lake directly, so some 'tables' a sync sees are projections over Parquet or CSV rather than managed storage. IBM AS/400: Standard access is SQL over JDBC/ODBC (commonly the open-source JTOpen driver), coexisting with legacy record-level access. Stacksync's field mapping accounts for these differences between Azure Synapse Analytics and IBM AS/400 without custom code.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 468 integrations available for Azure Synapse Analytics and IBM AS/400.