This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
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?
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 11 | |
| 10 | |
| 7 | |
| 7 | |
| 7 |
| User | Count |
|---|---|
| 28 | |
| 25 | |
| 22 | |
| 22 | |
| 20 |