Check which released records reached the archive this month.
Neil
- Once the connection is configured, I’ll use the records it provides and cite each one. Anything it doesn’t supply stays listed as missing.
- Reads
Selected Seal records
- Returns
- Records sent, destinations and failed transfers
- Missing or unmatched information
- Next steps for your team to review
1What’s connected.
Send selected Seal records to Snowflake for analysis and reporting through a connection set up with Seal’s API or Scripts. Agree the tables, refresh schedule, credentials and the source of record for each field.
Connection setup and permissions
Use Seal’s APIs or scripting engine for a connection tailored to your process. Agree the data mapping, access and direction of transfer before implementation.
2Load Seal records into Snowflake tables.
Route
PUT uploads files to an internal stage and COPY INTO loads them into a table. COPY can also load from external stages on Amazon S3, Google Cloud Storage or Azure.¹² Snowpipe loads files continuously as they arrive in a stage, and the SQL API is a REST API for submitting SQL.³⁴
Record identity
Primary key, unique and foreign key constraints are not enforced on standard tables, so a duplicate row is not refused.⁵ MERGE inserts, updates and deletes rows from a second table or subquery: the route for updating a row by its Seal identifier.⁶
Revisions
COPY skips files it has already loaded, remembering them for 64 days. FORCE = TRUE reloads them and can duplicate data.⁷² A changed file staged again under the same name gets a new checksum, and COPY treats it as new. Snowpipe does not: it ignores a file whose path and name it processed in the last 14 days, even if the content changed.²³ Time Travel reaches changed or deleted data within a retention period, one day by default.⁸
When it fails
- A load stops, or skips a file
- ON_ERROR defaults to ABORT_STATEMENT for bulk COPY and SKIP_FILE for Snowpipe.² Choose the setting deliberately: a skipped file is a missing set of Seal records.
- A corrected export never arrives
- Snowpipe ignores a file with a path and name it has already processed.³ Name each export after the Seal records and their versions, so a correction is a new file.
Check one record
Send one day’s batch records to a test table and count rows by Seal identifier: each should appear once. Then send a corrected record and confirm MERGE updated its row rather than adding a second.
3Start with the job.
Tell us what Neil needs to do and which records it needs. We’ll confirm the interface, permissions and implementation scope with your team.
4Before it goes live.
Access and any write-back
Define which records are in scope and whose permissions apply. Whether the connection writes back at all is a separate decision, with its own mapping and approval.
Verification and release
Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.
