Connection requirements
- An account identifier, warehouse, database, and schema, plus a user with INSERT/UPDATE on the target schema
MERGE-based upsert
Both the bulk load and CDC apply changes with a MERGE INTO ... WHEN MATCHED THEN UPDATE ... WHEN NOT MATCHED THEN INSERT statement, so the same code path handles first load and ongoing sync without a separate upsert branch.
Setup
1
Add the connection
Provide the Snowflake connection details under Connections → Add. NoSQLSync verifies it can connect before saving.
2
Pick a table name
Choose an existing table or let NoSQLSync create one from the inferred schema when the migration starts.
3
Start the migration
Bulk-load the historical data, then optionally enable CDC to keep the table current.
FAQ
Does NoSQLSync create the Snowflake table for me?
Yes. If the target table doesn't exist, it's created from the inferred schema before the first batch loads.
What happens if I re-run a migration that already has data in the target?
The bulk load switches to an idempotent upsert path instead of the empty-table fast path, so re-running is safe.