Two-way sync
Changes in Exasol or Full Enrich instantly reflect in both systems. No stale data, no manual imports.
Keep Exasol and Full Enrich in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Whatever Full Enrich is used for, it accumulates data the rest of the company wants to analyze, and that data usually sits behind an API rather than in the warehouse. Building and babysitting an extraction pipeline is the tax most teams pay for it.
Stacksync syncs Emails, Phone numbers, Credits, Enrichment requests from Full Enrich into tables in Exasol continuously, handling schema, rate limits, and retries. Because the sync is bi-directional, results computed in Exasol can also be written back into fields in Full Enrich where the tool can use them.
A continuously synced copy in Exasol preserves a queryable record even as data ages out of Full Enrich or gets changed inside it.
Records and events from Full Enrich land in Exasol as queryable tables, current within seconds and ready to join with the rest of the warehouse.
Combine Full Enrich's data with data from every other synced system to answer questions no single tool can.
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.
| Exasol objects | Full Enrich objects | How this pairing syncs | |
|---|---|---|---|
| Users and roles Grant read/write access for the dedicated integration account. | Credits Account balance consumed on successful finds; monitored to pace sync jobs. | Users and roles is specific to Exasol and Credits to Full Enrich — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that group the tables a sync reads from or writes into. | Enrichment requests Submitted batches of contacts to enrich; processed asynchronously by the waterfall. | Schemas is specific to Exasol and Enrichment requests to Full Enrich — each maps to any object or custom field on the other side. | |
| Tables Primary sync target; columnar relational tables written with standard SQL. | Contacts The person inputs (name plus company or domain) sent for enrichment. | Tables is specific to Exasol and Contacts to Full Enrich — each maps to any object or custom field on the other side. | |
| Views Read-only query surfaces often used as curated sources for reverse ETL. | Enrichment results Completed records fetched by request ID or delivered via webhook. | Views is specific to Exasol and Enrichment results to Full Enrich — each maps to any object or custom field on the other side. | |
| Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. | Emails Returned addresses with verification status, written back to the CRM or database. | Virtual schemas is specific to Exasol and Emails to Full Enrich — each maps to any object or custom field on the other side. | |
| UDF scripts In-database functions that can transform synced data after load. | Phone numbers Returned mobile and direct-dial numbers from the provider waterfall. | UDF scripts is specific to Exasol and Phone numbers to Full Enrich — 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 Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.
DeliveryEach detected change is written to Full Enrich through its API, with automatic retries and rate-limit backoff.
DetectionFull Enrich notifies Stacksync of record changes through webhook events. Webhook callbacks when enrichment batches complete, with polling of result endpoints as a fallback.
DeliveryEach detected change is applied to Exasol as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Exasol–Full Enrich connection.
Changes in Exasol or Full Enrich instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Exasol or Full Enrich data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Exasol or Full Enrich record.
Track your Exasol ⇄ Full Enrich sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Exasol and Full Enrich.
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 Exasol and Full Enrich 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 Exasol and Full Enrich 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 Exasol and Full Enrich: authenticate both systems, choose the objects to sync (such as Exasol's Users and roles and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
Full Enrich: Credits are consumed on successful finds, so integration logic should distinguish found, not-found, and in-progress outcomes when writing back. Exasol: Bulk loading uses the IMPORT statement, which is more efficient than row-by-row inserts for sync workloads. Stacksync's field mapping accounts for these differences between Exasol and Full Enrich without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Exasol and Full Enrich records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Exasol and Full Enrich connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Exasol–Full Enrich integration in-house.
Yes — Stacksync ships production-grade connectors for both Exasol and Full Enrich. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Exasol: Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients. On Full Enrich: Webhook callbacks when enrichment batches complete, with polling of result endpoints as a fallback. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 314 integrations available for Exasol and Full Enrich.