Snowflake's Query_tag functionality in Power Query?

[jersey417]

I'm currently trying to implement Snowflake's Query_Tag functionality within a number of reports to start tracking associated costs down to the workspace/report level.  I'm able to implement the following in Snowflake's Worksheets and the query run successfully. The query tag is loaded as expected in Snowflakes history query tag field. 

Example of the SQL currently being used;

---

ALTER SESSION SET QUERY_TAG = 'Workspace - Report';

SELECT  * 

FROM View

--- 

However, when I try to load the following SQL into the snowflake connector I get the following error.

I'd like to understand how to implement this via a native connect if possible. Has anyone had success getting this to work? 

[rkitch]

I had this same issue and wanted to track the cost of the PBI reports. I couldnt get the actual QUERY_TAG to work however a workaround we are doing is adding the query tag statement at the end of the query as a comment and then parsing out the QUERY_TEXT from ACCOUNT_USAGE to get the usage of the report. Hope that helps

[Franck_ecocert]

I'am interested too. I tried to pass an ALTER SESSION statement in the connection (with or without semicolon) :

But I have this error : Expression.Error: Native queries aren't supported by this value.

However I have a query in my Snowflake account 

I don't understant why Power BI encapsulate my query in a select * FROM ?

[Anonymous]

It doesnt work - please vote for the idea: https://ideas.powerbi.com/ideas/idea/?ideaid=50dd3f43-7595-ec11-826d-501ac5249847

[Anonymous]

Did anybody get this to work?

[jersey417]

No - The Snowflake connector needs to be updated to allow for the following.

[scottdigs]

I'm also interested in a solution for this for tracking reporting costs. In Tableau we can use 'Initial SQL' to accomplish this. However, Power BI seems to lack this functionality.

[jersey417]

@Anonymous 

Thanks - Both of those options are not resolving the issue.  When we move the semicolon it causes additional errors. 

[Anonymous]

Hi @jersey417 ,

1.It may casued by the semicolon in the end of the query,please delete it.

2. Please try @YMadden 's suggestion provided in this thread: Fully qualifying the table names as dbname.schemaname.tablename

Best Regards,
Eyelyn Qin
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.