Performance using Direct Query on Embedded Dashboard

Azure1 — Fri, 09 Dec 2016 16:51:27 GMT

When you deploy a dashboard using direct query to Azure, and embed it, and the datasource is an Azure SQL Database. Does it need to pull in the whole table when a user accesses it like it does when you use direct query with desktop? Or does it use the filters to narrow down the results into a smaller subset?

Re: Performance using Direct Query on Embedded Dashboard

tringuyenminh92 — Fri, 09 Dec 2016 17:44:00 GMT

Hi @Azure1,

For your questions:

Does it need to pull in the whole table when a user accesses it like it does when you use direct query with desktop? >> No, it just loads what needs to display and when you interactive with control in reports or after every ~15 minutes
Or does it use the filters to narrow down the results into a smaller subset? >> No, it's a mix between geneating query and memory cache - i will explain in next lines.

Cause when you/users interactive with filter, report will generate the query corresponding with that action and request to the sources (could be sql server and database engine).

I just quickly create small example as below picture:

when select filter options (i selected Male)query will be passed and executed in sources server

But the query for this action is only generated in first time and will be cached for the next actions. (you could go on to monitor the server side to verify this)
=> So there is no performance issue in here. it's perfect machanism

topic Re: Performance using Direct Query on Embedded Dashboard in Developer

Performance using Direct Query on Embedded Dashboard

Re: Performance using Direct Query on Embedded Dashboard