Two-way sync
Changes in Dremio or Snowflake instantly reflect in both systems. No stale data, no manual imports.
Keep Dremio and Snowflake in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Companies end up with two warehouses for practical reasons: a migration in progress, teams that standardized on different platforms, an acquisition, or tools that only connect to one of them. The result is the same dataset maintained twice, with duplicated pipelines and numbers that almost match.
Stacksync syncs tables between Dremio and Snowflake continuously, in either or both directions. Rows changed on one platform appear on the other within seconds, with schema and type mapping handled, so both warehouses answer questions with the same data.
Mirror the datasets a BI tool, notebook, or application needs onto the platform it can actually reach.
Where different teams run different warehouses, sync the curated tables both rely on so their metrics agree by construction.
Bring the acquired company's warehouse data across continuously instead of through one-off dumps.
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.
| Dremio objects | Snowflake objects | |
|---|---|---|
| Virtual datasets (views) SQL views layering semantics over physical data; the preferred sync target for curated extracts. | VARIANT Columns Semi-structured JSON payloads stored alongside relational columns. | |
| Apache Iceberg tables Lakehouse tables supporting DML and snapshot metadata usable for incremental reads. | Virtual Warehouses The compute a sync's queries run on, sized independently of storage. | |
| Spaces and folders Namespaces that organize virtual datasets and govern access. | Databases Top-level containers that scope which data a sync can touch. | |
| Reflections Materialized accelerations that make repeated extraction queries cheaper. | Schemas Namespaces within a database used to organize synced tables. | |
| Jobs Query execution records useful for monitoring sync workloads. | Tables The main landing and activation target for synced records. | |
| Sources Connected storage and database systems (S3, ADLS, relational databases) Dremio queries in place. | Views Modeled projections used as the source side of outbound syncs. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dremio–Snowflake connection.
Changes in Dremio or Snowflake instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Dremio or Snowflake data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Dremio or Snowflake record.
Track your Dremio ⇄ Snowflake sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Dremio and Snowflake.
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 Dremio and Snowflake 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 Dremio and Snowflake 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 Dremio and Snowflake: authenticate both systems, choose the objects to sync (such as Dremio's Virtual datasets (views) and Apache Iceberg tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Dremio: Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed. On Snowflake: Not explicitly stated; the setup script grants "create stream" on synced schemas (Snowflake streams), but the docs do not name the change-capture mechanism. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Dremio side: Physical datasets, Virtual datasets (views), Apache Iceberg tables, Spaces and folders, plus custom fields where Dremio exposes them. On the Snowflake side: Tasks, VARIANT Columns, Virtual Warehouses, Databases. 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 Dremio and Snowflake: Serve tools that only connect to one platform; Shared datasets across teams; Consolidation after M&A. Mirror the datasets a BI tool, notebook, or application needs onto the platform it can actually reach.
Dremio: Arrow Flight SQL, JDBC/ODBC, and a REST API. Authentication: Personal access tokens or username/password; OAuth-based SSO on Dremio Cloud. Snowflake: SQL via JDBC/ODBC and native drivers, plus the Snowflake SQL REST API. Authentication: Dedicated Snowflake service user + role with RSA key-pair authentication (Stacksync-provided public key), created via a setup script requiring SECURITY_ADMIN and ACCOUNTADMIN roles. 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 Dremio and Snowflake.