Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Is it possible to implement region-level security while ensuring queries remain fast?
Solved! Go to Solution.
Yes , it is possible to implement. It depends on how you model the data, for example apply the rls on dimregion table instead of facttable so that prunning will happen at early stage. the perfoarmance dependes on how complex dynamic cinditions are, if possible go for static rls if performace is priority.
Hope this will answer your doubt. if you are satisfied with answer please help to mark as solved and give a 👍 .
Thanks 😀
It can stay fast if you model it the “star-schema + small security table” way.
Star schema (one fact, region is a dimension key, not a text filter on the fact)
Security table is small (users ↔ regions mapping), not millions of rows
Filter flows User → Security bridge → Region dimension → Fact via keys (integers if possible)
Avoid complex many-to-many patterns directly into the fact unless absolutely necessary
Hi @Ericathomas ,
May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.
Thank you.
Hi @Ericathomas ,
Thank you @cengizhanarslan , @FBergamaschi, @AmitDevkatte for your response.
We’d like to follow up regarding the recent concern. Kindly confirm whether the issue has been resolved, or if further assistance is still required. We are available to support you and are committed to helping you reach a resolution.
Thank you for your patience and look forward to hearing from you.
Best Regards,
Chaithra E.
It can stay fast if you model it the “star-schema + small security table” way.
Star schema (one fact, region is a dimension key, not a text filter on the fact)
Security table is small (users ↔ regions mapping), not millions of rows
Filter flows User → Security bridge → Region dimension → Fact via keys (integers if possible)
Avoid complex many-to-many patterns directly into the fact unless absolutely necessary
Yes , it is possible to implement. It depends on how you model the data, for example apply the rls on dimregion table instead of facttable so that prunning will happen at early stage. the perfoarmance dependes on how complex dynamic cinditions are, if possible go for static rls if performace is priority.
Hope this will answer your doubt. if you are satisfied with answer please help to mark as solved and give a 👍 .
Thanks 😀
Hi @Ericathomas,
yes, absolutely, with Row Level Security, static or dynamic, based on your needs.
If this helped, please consider giving kudos and mark as a solution
@me in replies or I'll lose your thread
Want to check your DAX skills? Answer my biweekly DAX challenges on the kubisco Linkedin page
Consider voting this Power BI idea
Francesco Bergamaschi
MBA, M.Eng, M.Econ, Professor of BI
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 48 | |
| 45 | |
| 41 | |
| 19 | |
| 17 |
| User | Count |
|---|---|
| 68 | |
| 67 | |
| 34 | |
| 31 | |
| 30 |