Question

A data engineer has configured Snowpipe with auto-ingest to continuously load files from an external S3 stage into a landing table. Files are arriving, but some do not seem to appear in the target table. The engineer needs to determine which specific files were loaded, which were skipped, and any errors encountered by the pipe over the last several hours. Which approach should the engineer use to investigate the pipe's load activity?

Accepted Answer

Query the COPY_HISTORY table function in the Information Schema (or ACCOUNT_USAGE), filtering on the target table and time range to see per-file load status and errors

Answer

Run LIST on the external stage to compare the files present against the rows in the target table

Answer

Execute a COPY INTO statement with VALIDATION_MODE = RETURN_ERRORS against the same stage to reproduce the errors

Answer

Query the LOAD_HISTORY view in the Information Schema to view Snowpipe file-level load results