SOL-C01 · Question #273
A data engineer executed several queries in Snowflake using Snowsight, and now needs to identify the specific queries that inserted data into the 'SALES TABLE' table within the 'SALES DB' database and
The correct answer is C. using the 'Text' filter in Query History with the search string 'INSERT INTO. The Text filter in Snowsight's Query History allows you to search for queries containing a specific string. By entering 'INSERT INTO SALES_TABLE' (or the fully qualified 'INSERT INTO SALES_DB.PUBLIC.SALES_TABLE'), the filter returns only queries whose SQL text matches that patter
Question
A data engineer executed several queries in Snowflake using Snowsight, and now needs to identify the specific queries that inserted data into the 'SALES TABLE' table within the 'SALES DB' database and 'PUBLIC' schema. Which Snowsight feature or filtering option within the Query History interface is MOST effective for achieving this?
Options
- AFiltering the Query History by the 'User' who executed the queries.
- BFiltering the Query History by the 'Warehouse' used during query execution.
- Cusing the 'Text' filter in Query History with the search string 'INSERT INTO
- DFiltering the Query History by 'Status' to only show 'Successful' queries.
- EFiltering the Query History using the 'Query ID' field to narrow down the list.
How the community answered
(55 responses)- B2% (1)
- C93% (51)
- D2% (1)
- E4% (2)
Explanation
The Text filter in Snowsight's Query History allows you to search for queries containing a specific string. By entering 'INSERT INTO SALES_TABLE' (or the fully qualified 'INSERT INTO SALES_DB.PUBLIC.SALES_TABLE'), the filter returns only queries whose SQL text matches that pattern, directly identifying the INSERT operations on the target table. This is the most precise and direct method for this use case. Option A (filter by User) narrows results to queries from a specific person but doesn't identify what those queries did to which table. Option B (filter by Warehouse) narrows results by compute resource used, irrelevant to query content. Option D (filter by Status: Successful) removes failed queries but still leaves all types of successful queries-SELECTs, UPDATEs, DDL-in the results. Option E (filter by Query ID) requires already knowing the specific IDs, which defeats the purpose of the investigation.
Topics
Community Discussion
No community discussion yet for this question.