Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowTry your skills in the Power BI Dataviz World Championship! Round one ends June 26. Join now
I am working on a dashboard that will be using Direct Query to several large tables (100M rows). Row level filtering is being used to filter the results. From the query logs, we see that PowerBI is loading the full dataset each time, instead of pushing the filtering selection down to the SQL level. This is causing unacceptable wait times. Is there any way to have PowerBI force the filtering predicate down to the SQL query level?
@Jlacenski wrote:
I am working on a dashboard that will be using Direct Query to several large tables (100M rows). Row level filtering is being used to filter the results. From the query logs, we see that PowerBI is loading the full dataset each time, instead of pushing the filtering selection down to the SQL level. This is causing unacceptable wait times. Is there any way to have PowerBI force the filtering predicate down to the SQL query level?
That's some limitation on the Direct Query, especially applying RLS on a huge dataset. Check Important considerations when using DirectQuery.
Can you break down the report to sub reports? 100M rows is quite huge.
Hi,
Adding to a similar note, is there a limitation to the number of rows, after which the processing according to you would become slower? I deal with roughly 50K rows in my reports where RLS is applied at the Power BI level and was wondering if the solution would scale considering the limited amount of data?
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 16 | |
| 11 | |
| 11 | |
| 8 | |
| 7 |
| User | Count |
|---|---|
| 36 | |
| 33 | |
| 31 | |
| 29 | |
| 20 |