Forum Discussion
Two snowflake users in PowerBI services
Hi Everyone,
Problem Background:
I have two workspaces in powerbi services.
Workspace A, Workspace B.
Workspace A has a report "management report" which contains data from snowflake from a different database (two schemas) and for this report I created a different user "management_user" and gave only management related data access in snowflake to this user. In powerbi I'm using this user credentials with privacy level public.
Workspace B has a report "marketing_report" which also contains data from snowflake but from a different database, also for this report I have a different user in snowflake "marketing_user" and gave only management related data access in snowflake to this user. In powerbi I'm using this user crendentials for this report with privacy level private.
Problem:
Keep in view that both reports are using their respective users and passwords. if managment_user is being used, then it powerbi services do not refreshes the marketing_report (despite that marketing report has its own different user), and vice versa. Any leads will be much appreciated.
- Anonymous2 years ago
Hi asifrasool ,
Based on the information you provided, the core of the issue appears to be using a different Snowflake user and different privacy level settings for each report in Power BI. Here are some insights and steps you can take to troubleshoot and resolve the potential issue:
- Ensure that the data source credentials for both Snowflake users (management_user and marketing_user) are configured correctly in their respective workspaces. This includes verifying that the credentials have not been inadvertently overwritten or expired.
- Differences in privacy levels ("public" for management_user and "private" for marketing_user) may affect refresh behaviour. As you are using different databases and schemas, consider setting both to the same privacy level, preferably the "organisation" level, to maintain a balance between data isolation and functionality. For more information on privacy levels, see Privacy levels in Power BI Desktop.
- Check the scheduled refresh configuration for both reports in their respective workspaces. Ensure that there are no conflicts or limitations that could affect the refresh operation.
Best Regards,
Ada Wang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
5 Replies
- lbendlinSuper User
Is it really a different database, or only a different schema?
- asifrasoolHelper I
lbendlin yes for sure those are really two different databases.
- lbendlinSuper User
In that case you should not have an issue creating separate gateway connections.
- AnonymousNot applicable
Hi asifrasool ,
Based on the information you provided, the core of the issue appears to be using a different Snowflake user and different privacy level settings for each report in Power BI. Here are some insights and steps you can take to troubleshoot and resolve the potential issue:
- Ensure that the data source credentials for both Snowflake users (management_user and marketing_user) are configured correctly in their respective workspaces. This includes verifying that the credentials have not been inadvertently overwritten or expired.
- Differences in privacy levels ("public" for management_user and "private" for marketing_user) may affect refresh behaviour. As you are using different databases and schemas, consider setting both to the same privacy level, preferably the "organisation" level, to maintain a balance between data isolation and functionality. For more information on privacy levels, see Privacy levels in Power BI Desktop.
- Check the scheduled refresh configuration for both reports in their respective workspaces. Ensure that there are no conflicts or limitations that could affect the refresh operation.
Best Regards,
Ada Wang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- asifrasoolHelper I
Hi Anonymous thank you for suggesting work around. It was really a strange behaviour. When I used to refresh manually it had always given me the error, when it ran on scheduled refreshes, it worked fine.