Real-time
Two-way sync
Changes in MotherDuck or OCI Database (Oracle Cloud) instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ Database
MotherDuck to OCI Database (Oracle Cloud) integration — real-time, two-way sync
Keep MotherDuck and OCI Database (Oracle Cloud) in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect MotherDuck and OCI Database (Oracle Cloud)
Connect OCI Database (Oracle Cloud) and MotherDuck with one live, two-way sync: operational rows flow into the warehouse, and computed results flow back where systems can read them fast.
Operational databases and analytical warehouses want the same data at different moments. Analysts want OCI Database (Oracle Cloud)'s rows in MotherDuck, 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 OCI Database (Oracle Cloud) where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in OCI Database (Oracle Cloud) sync into MotherDuck in real time, and result tables in MotherDuck sync back into OCI Database (Oracle Cloud), with schema and type mapping between the two systems handled for you.
Common use cases
- 01 Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management
- 02 Sync modeled MotherDuck tables outward to operational tools for activation
- 03 Run on-prem Oracle and OCI side by side during a cloud migration while keeping both ends writable.
- 04 Expose ERP or billing data held in OCI to internal tools by syncing selected schemas to a managed Postgres.
Common sync patterns
Fresh analytics without loading windows
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Offload heavy reads
Point analytical queries at the synced copy in MotherDuck and keep OCI Database (Oracle Cloud) focused on its operational workload.
Operational data in the warehouse, minus the pipeline
Rows from OCI Database (Oracle Cloud) land in MotherDuck as they change, replacing hand-built CDC and batch extract jobs.
What you can sync between MotherDuck and OCI Database (Oracle Cloud)
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.
| MotherDuck objects | OCI Database (Oracle Cloud) objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Namespaces within a database used to organize synced tables. | Schemas Namespace boundaries that scope which objects a sync connection can access | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Tables The main landing target for synced records and source for analysis. | Tables The primary sync surface; rows are read and written directly over SQL | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Views Modeled projections used as outbound sync sources. | Views Read-only projections used to expose curated subsets to downstream systems | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Database Shares Read-only copies of a database shared with other users or teams. | Sequences Key generators that matter when writing new rows from external systems | Database Shares is specific to MotherDuck and Sequences to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side. | |
| Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. | PL/SQL procedures and packages Server-side logic that can react to synced data or transform it in place | Attached Local DuckDB Databases is specific to MotherDuck and PL/SQL procedures and packages to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side. | |
| Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. | JSON collections Document-style storage in the converged engine, synced alongside relational tables | Databases is specific to MotherDuck and JSON collections to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side. |
How changes propagate between MotherDuck and OCI Database (Oracle Cloud)
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.
MotherDuck OCI Database (Oracle Cloud) Interval-based propagation
DetectionStacksync polls MotherDuck for changes on an incremental schedule, reading only records changed since the previous pass. Polling.
DeliveryEach detected change is applied to OCI Database (Oracle Cloud) as a row-level write, with types converted between the two schemas.
OCI Database (Oracle Cloud) MotherDuck Sub-second propagation
DetectionChanges in OCI Database (Oracle Cloud) are captured at the source via change data capture — no polling loop against its API. Log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling.
DeliveryEach detected change is applied to MotherDuck as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- MotherDuck: Subject to the platform's compute and concurrency limits rather than per-request API rate limits.
- OCI Database (Oracle Cloud): Throughput bounded by instance sizing rather than API quotas.
What ships with MotherDuck ⇄ OCI Database (Oracle Cloud)
Connect MotherDuck and OCI Database (Oracle Cloud) for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MotherDuck–OCI Database (Oracle Cloud) connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever MotherDuck or OCI Database (Oracle Cloud) data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single MotherDuck or OCI Database (Oracle Cloud) record.
Observability
Monitoring
Track your MotherDuck ⇄ OCI Database (Oracle Cloud) sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between MotherDuck and OCI Database (Oracle Cloud).
How the MotherDuck and OCI Database (Oracle Cloud) connectors work
MotherDuck
- Integration surface
- SQL through DuckDB clients and drivers using a MotherDuck (md:) connection
- Authentication
- Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults
- Change detection
- Polling; no log-based CDC or webhook surface is exposed
- Capabilities
- read · write
- Rate limits
- Subject to the platform's compute and concurrency limits rather than per-request API rate limits
OCI Database (Oracle Cloud)
- Integration surface
- SQL wire protocol (Oracle Net) via JDBC, ODBC, and native drivers; ORDS REST optionally exposes tables over HTTP
- Authentication
- database credentials, commonly with mutual TLS using a client wallet on Autonomous Database; OCI IAM integration available
- Change detection
- log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling
- Capabilities
- read · write · CDC
- Rate limits
- throughput bounded by instance sizing rather than API quotas
How it works
How to connect MotherDuck to OCI Database (Oracle Cloud) — three steps, no code
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.
- 01
Connect your apps
Authenticate MotherDuck and OCI Database (Oracle Cloud) with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
MotherDuck
connected
OCI Database (Oracle Cloud)
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the MotherDuck and OCI Database (Oracle Cloud) 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.
objects · MotherDuck ⇄ OCI Database (Oracle Cloud)Customers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
MotherDuck OCI Database (Oracle Cloud)Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
MotherDuck and OCI Database (Oracle Cloud) integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between MotherDuck and OCI Database (Oracle Cloud): authenticate both systems, choose the objects to sync (such as MotherDuck's Schemas and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both MotherDuck and OCI Database (Oracle Cloud). The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on MotherDuck: Polling; no log-based CDC or webhook surface is exposed. On OCI Database (Oracle Cloud): Log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the MotherDuck side: Schemas, Tables, Views, Database Shares, plus custom fields where MotherDuck exposes them. On the OCI Database (Oracle Cloud) side: Sequences, PL/SQL procedures and packages, JSON collections, Partitions. 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 MotherDuck and OCI Database (Oracle Cloud): Fresh analytics without loading windows; Offload heavy reads; Operational data in the warehouse, minus the pipeline. Because changes stream continuously, analysts query current data instead of waiting for last night's load.
SECURITY
Security teams trust Stacksync
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.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
