Forum Discussion
Direct Query to Dataflows: What would the downsides be | Solves any dataset size limits it seem
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.