DirectQuery: How to view generated SQL per visual, with row count and execution time?

[TeeGee]

I am working with a fairly complex (5 slicers, 13 visuals) Power BI report that is attached to an Azure SQL database via DirectQuery.

Currently, I am examining the generated SQL via the SQL Server Query Store, which works "ok", but one downside is, there's no way of knowing which visual corresponds to each SQL statement.

Is there an alternative approach to debugging SQL where I would be able to see this association, and hopefully still see row count and execution time per statement?

[v-chuncz-msft]

@TeeGee,

DAX Studio can be used to capture queries, you may have a look.

[TeeGee]

DAX Studio doesn't show which query belongs to which Visual though does it?

[srinivt]

The only thing you could do is move each of your visuals to a page of their own. Now when you reopen your pbix file, the queries will be sent only for your active page, which could help you to debug and relate it to the corresponding SQL query/queries. 

[TeeGee]

Well sure, you can do that, but if you have a poorly performing piece of SQL that you notice executing on the backend, having to go through a trial and error process to find out which visual it belongs to is not a great use of a person's time.  Yes, I realize that based on the contents of the query you can very often (but not always!) narrow it down to a smaller subset of visuals to consider, but the point is, you shouldn't have to do this.  Microsoft devs control this entire stack, outputting the underlying visual with the SQL shouldn't be terribly technically difficult I wouldn't think.

Rumor has it this change is in the queue somewhere, so hopefully it isn't too far down the list.