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
Improve Copy Job Validation Errors When Upsert Keys Are Missing
Improve Copy Job Validation Errors When Upsert Keys Are Missing Product: Microsoft Fabric Area: Data Factory – Copy Job Category: Error Handling / User Experience Problem When adding new tables ...jasonhorner43 minutes agoRegular VisitorNew3Views0likes0Comments📉 How Would You Investigate a 20% Drop in Revenue?
A data analyst shouldn’t stop at identifying what happened. The real questions are: Where did the decline occur? → Why did it happen? → What caused it? → What should we do next? By analyzing regio...aliulmurtaza2 hours agoNew MemberNew4Views0likes0CommentsAdd “Don't show this again” option to Power Query Insert Step warning
When a transformation is performed while an earlier Applied Step is selected, Power Query displays the “Insert Step” warning every time. This is useful for new users, but becomes unnecessary for expe...bjs17465 hours agoNew MemberNew3Views0likes0Comments