A table is loaded using Snowpipe and truncated afterwards. Later, a Data Engineer finds that the table needs to be reloaded, but the metadata of the pipe will not allow the same files to be loaded…

Question

Options

• AWait until the metadata expires and then reload the file using Snowpipe.
• BModify the file by adding a blank row to the bottom and re-stage the file.
• CSet the FORCE=TRUE option in the Snowpipe COPY INTO command.
• DRecreate the pipe by using the CREATE OR REPLACE PIPE command.

• A
  17% (9)
• B
  7% (4)
• C
  4% (2)
• D
  72% (39)

Explanation

Recreating the pipe with CREATE OR REPLACE PIPE resets the pipe's load metadata, which is what tracks previously ingested files - this single DDL command clears the history and allows the same staged files to be loaded again with no manual file manipulation or waiting required.

Option A is wrong because Snowpipe metadata persists for up to 64 days by default, making the wait operationally impractical. Option B is wrong because manually editing files to trick the deduplication check is error-prone, introduces data quality risk, and requires re-staging - high overhead. Option C is a trap: FORCE=TRUE is a valid option for a standalone COPY INTO command, but modifying a Snowpipe's internal COPY INTO to add it would require recreating the pipe anyway, making it equivalent to D but with extra steps.

Memory tip: Think of a pipe as having a "loaded files diary." CREATE OR REPLACE PIPE tears out the diary and starts fresh - one command, zero history.

No community discussion yet for this question.