Forum Discussion

jarwest's avatar
jarwest
Icon for Helper II rankHelper II
8 months ago
Solved

Is it possible to force specific reports to utilize specific Gateway Members of a Clustered Gateway?

Hey all,

I have an On-Prem Gateway made of multiple devices acting as Gateway Members. One of our newer Gateway Members is having difficulty with connecting to one specific external data source that the other 2 are connecting to fine. Is it possible to have Load Balancing Between Gateway Members enabled while forcing the few specific reports to utilize any Gateway Member except for the one that is not functioning properly with that data source?

I know this is not the best practice solution, however I'm hoping to get something working to deal with a time constraint while trying to discuss the issue with the external data source owner, who is uncooperative in allowing a 3rd device access.

I can't find anything on the topic anywhere, so I am admittedly asking so I can take any information on the subject back to my team, even if it's as simple as 'this is not a supported feature of PBI Service at this time'.

Happy Friday!

3 Replies

  • Reports do not use gateways, semantic models do. This is only relevant for report users where one or more of the semantic model on-premise data sources are in Direct Query mode.  When a report user runs such a query (by interacting with the visual) the Power BI service will randomly use one of the gateway cluster members and ask it to process that query.  Neither you nor the report user have any control over that.

     

    If this is important to you please consider voting for an existing idea or raising a new one at https://ideas.fabric.microsoft.com

  • Scenario

    Supported

    Force specific reports to avoid one gateway member

    No but somehow it possible, you can avoid adding users in that gateway permissions and those reports should have in separate workspace, one dedicated gateway should be established for those particular reports.

    Control load balancing rules

    No

    Exclude a gateway member for a single data source

    No

    Gateway member affinity / pinning

     No

    Gateway cluster health-based failover

    Yes

    Multiple gateways per tenant

    Yes