QUERY_HISTORY has no PARENT_QUERY_ID. Here's how I traced which statement inside a Snowflake procedure regressed anyway.

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 yo...