When Power BI connects to Snowflake using a credential that has access to many roles (more than 25) vs. another credential that has fewer roles (less than 5), the response time is significantly poorer (3x to 10x slower)
We have learned that Power BI is exhaustively examining all the roles and their security allowances, before doing the work of the query.
Other tools - Tableau, Business Objects, do this without this extreme overhead. They simply evaluate if the current role can run the current query and let the database backend be the gatekeeper.
As a result - Snowflake, which is orders of magnitude faster than traditional on-prem databases, ends up being slower in Power BI
Suggestion: Let the backend database do the security reconciliation. Streamline Power BI's examination of role metadata to do what Power BI competitors do before running the query
1 Comment
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
Org apps - Cannot be arranged in folders and do not stay hidden
Currently, Organizational Apps (Org Apps) are displayed in the standard Apps section of the Get Apps experience, alongside regular workspace apps. For organizations managing large-scale Power BI depl...akonda15 hours agoNew MemberNew6Views0likes0CommentsIncrease or Make Configurable the Power BI Browser Tab Limit (Currently 20 Items)
Power BI users frequently work across multiple reports, dashboards, semantic models, notebooks, and Fabric artifacts simultaneously. The current browser limitation of 20 open Power BI/Fabric items re...sharadmahajan17 hours agoRegular VisitorNew339Views21likes3CommentsAdd "NO SELECTION" default selected option to slicers
Scenario Currently, slicers have two states: No value selected (bogs report down) BI dev preselects one or more data values (problematic when reports are consumed by other clients/users) Option...arpost19 hours agoPost ProdigyNew8Views0likes0Comments