Which query can be used to find all the file loading errors through Snowpipe in the last 1 hour?

• A. select * from table(information_schema.copy_history(table_name=>'MY_TABLE', start_time=> dateadd(hours, -1, current_timestamp())));
• B. select * from table(information_schema.load_history(table_name=>'MY_TABLE', start_time=> dateadd(hours, -1, current_timestamp())));
• C. select * from information_schema.load_history order by last_load_time desc limit 10;
• D. select * from table(information_schema.copy_history(table_name=>'MY_TABLE', start_time=> current_timestamp()));

Answer: (A)

Snowpipe loads are performed via COPY INTO, and each COPY INTO operation for a table is recorded in the information schema’s copy_history. The key is to pull those copy events within a defined time window and inspect any indicator of failure, such as a non-success status or a nonzero error_count. By filtering copy_history with the table name and a start_time of dateadd(hours, -1, current_timestamp()), you get every load attempt started in the last hour for that table, including any that failed, so you can surface the file loading errors. The results include details like start_time, end_time, status, file_name, and error_count, which lets you pinpoint exactly which loads had errors and inspect the accompanying messages. Using the load_history view or querying without a time bound either doesn’t target Snowpipe’s copy events as precisely or doesn’t constrain the window to the last hour, making the chosen approach the most accurate for this task.