Two-way sync
Changes in Full Enrich or SQL Server instantly reflect in both systems. No stale data, no manual imports.
Keep Full Enrich and SQL Server in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Engineers integrate with tools like Full Enrich through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in SQL Server.
Stacksync mirrors Credits, Enrichment requests, Contacts, Enrichment results from Full Enrich into Stored Procedures, Databases, Schemas, Tables in SQL Server and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Full Enrich, so the tool and the database never disagree.
Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
Records from Full Enrich are ordinary rows in SQL Server; join them, index them, and use them in application logic without touching the vendor API.
Write to the synced tables in SQL Server and Stacksync propagates the change into Full Enrich, replacing custom integration code.
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.
| Full Enrich objects | SQL Server objects | |
|---|---|---|
| Credits Account balance consumed on successful finds; monitored to pace sync jobs. | Stored Procedures T-SQL logic that can validate or post-process synced rows. | |
| Enrichment requests Submitted batches of contacts to enrich; processed asynchronously by the waterfall. | Databases Instance-level databases that scope a sync's reads and writes. | |
| Contacts The person inputs (name plus company or domain) sent for enrichment. | Schemas Namespaces (dbo and custom) used to organize synced tables. | |
| Enrichment results Completed records fetched by request ID or delivered via webhook. | Tables The primary sync target; rows map to records in connected systems. | |
| Emails Returned addresses with verification status, written back to the CRM or database. | Views Read-side projections used as outbound sync sources. | |
| Phone numbers Returned mobile and direct-dial numbers from the provider waterfall. | Columns Field-level mapping targets with T-SQL types. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Full Enrich–SQL Server connection.
Changes in Full Enrich or SQL Server instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Full Enrich or SQL Server data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Full Enrich or SQL Server record.
Track your Full Enrich ⇄ SQL Server sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Full Enrich and SQL Server.
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 Full Enrich and SQL Server 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 Full Enrich and SQL Server 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 Full Enrich and SQL Server: authenticate both systems, choose the objects to sync (such as Full Enrich's Credits and Enrichment requests), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Full Enrich: Webhook callbacks when enrichment batches complete, with polling of result endpoints as a fallback. On SQL Server: SQL Server Native Change Data Capture (CDC); a DBA runs a one-time setup script with sysadmin privileges to enable CDC and create Stacksync wrapper procedures. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Full Enrich side: Credits, Enrichment requests, Contacts, Enrichment results, plus custom fields where Full Enrich exposes them. On the SQL Server side: Stored Procedures, Databases, Schemas, 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 Full Enrich and SQL Server: One integration pattern for the whole stack; Read Full Enrich with a query; Automate Full Enrich from your codebase. Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
Full Enrich: REST API with asynchronous bulk enrichment endpoints. Authentication: API key (Bearer token). SQL Server: SQL over the TDS wire protocol (Tabular Data Stream), via ODBC/JDBC/ADO.NET drivers. Authentication: Database credentials entered as a connection string or as parameters (host/user/password) in the Create New Sync page. Stacksync manages authentication, retries, and rate limits on both sides.
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 386 integrations available for Full Enrich and SQL Server.