If you write ETL procedures in Snowflake but don't have ACCOUNT_USAGE access, you've probably had this exact conversation: someone says a load job got slower, you can look at one query's profile if you already know which query, but QUERY_HISTORY gives you zero help connecting a CALL to the statem...
Source: [Dev.to](https://dev.to/tracepointdata/queryhistory-has-no-parentqueryid-heres-how-i-traced-which-statement-inside-a-snowflake-el7)