A data analyst clicks on a query in Query History and notices that the Query Profile panel shows 'Query profile is not available' for that execution. What is the MOST likely reason for this message?
Answer & explanation
Correct answer: E
WHY E: The documentation states that a Query Profile is not available for queries that run from the query cache. To bypass the cache and get a fresh profile, the analyst makes a trivial change to the query, such as altering or removing the LIMIT clause.
WHY NOT A: There is no documented minimum duration for generating a Query Profile; short queries produce profiles when they are actually executed.
WHY NOT C: Viewing a profile requires being the query owner or having CAN MONITOR (not CAN MANAGE) on the warehouse, and a missing permission is not what this message indicates.
WHY NOT D: Query Profiles are also accessible from notebooks attached to SQL warehouses or serverless compute, not just from the SQL editor.
WHY NOT B: Query Profiles are generated for successfully completed queries; the cache, not the success or failure status, is what suppresses the profile.