← Help Center
Warehouse
Snowflake (script over the S3 export)
Snowflake reads the S3 export: set up an S3 destination, then run the generated script (a stage on your bucket and one COPY INTO per table) in Snowflake. Snowflake's SQL API has no PUT, so OrcLink cannot load Snowflake directly without your bucket.
Built, not yet tested liveBuilt. Not yet tested against a live Snowflake account.
Live: shipped in OrcLink's production release before this one. Built, not yet tested live: built and tested with sample data, not yet run against a live account of the vendor. Coming soon: listed, not available to connect yet.
How to connect
- Set up an Amazon S3 destination first. Then Data out > Warehouse > Snowflake script: database, schema, storage integration, table prefix and a day; run the generated script (a stage on your bucket and a COPY INTO per table) in Snowflake.
What OrcLink reads
- Nothing from the destination.
What OrcLink writes back
- Nothing from OrcLink to Snowflake: Snowflake reads the files of your S3 export with the script. OrcLink cannot load Snowflake directly without your bucket.
Never stored
- Your credentials in clear: stored encrypted (AES-256-GCM) and never shown again.
Known limits
- Whether COPY INTO runs inside the script's transaction is not yet checked on a live Snowflake account.
- Files are CSV (gzip); Parquet is not built.
- HIPAA mode: it runs only when the workspace has accepted OrcLink's BAA and an owner has recorded a BAA with the vendor; campaign names only with "Include campaign names in data out".
- It runs only while the person who set it up (or last started it) can still manage the workspace.
- Plans: the warehouse export needs the Medium plan or above.