Refresh for DirectQuery dataset vs Publish to web

[PetyrBaelish]

I have a dataset in the Power BI Service; this dataset involves a DIrect Query to anon-premises data source. An On-Premises Data Gateway is in operation for this.

The business user wants to publish a report that uses this dataset to the web (there's no sensitive data here). My concern is the web traffic that views this report could be such a high volume that it brings down the databasde server contianing the data source, for example a program written to maliciously keep pinging the report at a high frequency.

Is this a legitimate concern?

Being DirectQuery, does each view/interaction of the report cause a refresh that will generate traffic to my on-premises server?

If yes, is there anything I can do in Power BI Service or my gateway's data source to mitigate this risk?

[v-xicai · Accepted solution]

Hi @PetyrBaelish ,

When you use Publish to web ,as users view the report, either by opening the direct public URL or viewing it embedded in a web page or blog, Power BI caches the report definition and the results of the queries required to view the report. This ensures that thousands of concurrent users can view the report without impacting performance.

You can learn more:

https://docs.microsoft.com/en-us/power-bi/service-publish-to-web#how-it-works-technical-details,

https://docs.microsoft.com/en-us/power-bi/service-publish-to-web#updates-to-reports-and-data-refresh.

Best Regards,

Amy

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