Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

July 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more

Reply
mmace1
Impactful Individual
Impactful Individual

Direct Query to Dataflows: What would the downsides be | Solves any dataset size limits it seem

Circa the June 2021 release of Power BI, direct query to dataflows is now generally supported (in Premium). Just offhand:

Pros:

  • Your dataset can always be small if everything you pull in is a Dataflow - so no matter if you have 100s of millions of facts, with 100s of thousands of entries in your dimensions - no problem.

Cons:

  • Direct Query, so no adding additional columns, either in PQ, or DAX.
  • Performance?

Seems like a big thing. Then again, I'm not sure how many places have the volume of (actually relevant) high cardinality that my shop does and/or if I'm missing something. 

1 ACCEPTED SOLUTION
jeffshieldsdev
Solution Sage
Solution Sage

The data goes into a table in managed SQL store. I'm not sure if any indexes are automatically created.

We've found performance slow, but just in POC testing and that was with a table with high cardinality and lengthily text (URLs).

I imagine you have to build dataflows that precisely fit your use case and probably leverage aggregations in your model too. Perhaps creating lookup tables and importing those in a composite model will improve performance also.

View solution in original post

5 REPLIES 5
jeffshieldsdev
Solution Sage
Solution Sage

The data goes into a table in managed SQL store. I'm not sure if any indexes are automatically created.

We've found performance slow, but just in POC testing and that was with a table with high cardinality and lengthily text (URLs).

I imagine you have to build dataflows that precisely fit your use case and probably leverage aggregations in your model too. Perhaps creating lookup tables and importing those in a composite model will improve performance also.

@jeffshieldsdev 

Thanks for the feedback on testing-speed. 

Our biggestcovers-most-things model, which is at the most granular level, just went over 1GB.  So given we're on P1 Premium, we're doing *OK* at the moment, but the stupid company is growing quickly. 

It's the nature of our business as well- we have 2 different dimensions that are in the millions of rows & growing, so even grouping the facts still leaves a ton. 

By lookup table do you mean just a dimensions in proper demnormalized star schema, or...? 




Yes, that's right--put the dimensions you'll want in slicers into their own table in Import mode and relate to your fact table.

Yes, that's right--put the dimensions you'll want in slicers into their own table in Import mode and relate to your fact table.

And importing them - got it.  Thanks. 

Helpful resources

Announcements
FabCon and SQLCon Barcelona 2026

FabCon & SQLCon – Barcelona 2026

Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.

60 days of Data Days Carousel

Data Days 2026

Join Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

Top Solution Authors