The assumption is that they're in different reports and can be separated. For example, try to separate DirectQuery data sources from scheduled refresh data sources whenever possible. To learn more about connection types and supported data sources, see the list of available data source types.ĭepending on which type of connection is used, gateway usage can be different. Many factors might contribute to your choice of one over the other, such as security requirements, performance, data limits, and data model sizes. Not all data sources support both connection types. Power BI offers two types of connections: DirectQuery and Import. In this way, you distribute the gateway load among the multiple reports that contribute to the single dashboard. If a dashboard is based on multiple reports, you can use a dedicated gateway for each contributing report. Even if a report is based on multiple data sources, all such data sources must go through a single gateway. See the following sections for performance counters and minimum requirements that can help you determine whether a machine is adequate.Ī constraint in Power BI allows only one gateway per report.
If all the users access a given report at the same time each day, make sure that you install the gateway on a machine that's capable of handling all those requests.
This article provides guidance and considerations for deploying a data gateway for Power BI in your network environment.įor information about how to download, install, configure, and manage the on-premises data gateway, see What is an on-premises data gateway?. To provide feedback on this article, or the overall gateway docs experience, scroll to the bottom of the article. You're currently in the Power BI content. We've split the on-premises data gateway docs into content that's specific to Power BI and general content that applies to all services that the gateway supports.