Forum Discussion
Helper VFabric - rows per table limitation
300M is the row limit per table in an F8 SKU where DirectLake will be supported. Any tables above 300M when running on an F8 capacity will fall back to DirectQuery.
Helper Vwe made some tests and compared a table of 300M rows with one of +300M rows
direct lake mode could not be used for the second one
some of the descriptions below are in swedish but you should be able to understand what teh tables show
300M (for F8 capacity in our case) is not a hard limit for storing but for consumption it is significant limitation
Community ChampionIf I understand correctly, it shows that Direct Lake outperforms DirectQuery significantly.
So the row limit for Direct Lake needs to be taken into account when considering which SKU to buy.
Perhaps it's possible to trick the system by splitting the fact table into 2 tables and then use measure to "append them"? 🤔😄
- joakimfenno
yes, I can see different workarounds (splitting into different tables and combining with common measures for example) but no solution that is satisfying
I did split fact tables 15 years ago before partitioning came around 🙂