Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes! Register now.
Hi,
I noticed some differences between the lakehouse and the data warehouse and I'm not much sure why these differences are there.
The lakehouse:
The Data Warehouse:
The questions about these differences:
Thank you in advance !
I think that they have different purposes - the major one being that a warehouse supports DML as well as DDL vs the Lakehouse only supporting DML.
There are other nuances e.g. max size for a varchar field in warehouse is 4000 in lakehosue it is 8000
We leverage a warehouse primarily as it meets our needs (source to drive powerbi reporting) - but we do have some items in the lakehouse (large unstructured text fields)
In short I dont think its a case of either or more a case of what fits my use case / what are my team more comfortable with
Hi, @BryanCarmichael ,
The point is about the storage differences I mentioned in the question.
Both are stored in OneLake, the storage for the entire Microsoft Fabric. However, they follow almost opposite behaviours, as I highlighted above. So, the questions about storage mentioned....
Kind Regards,
Dennes
User | Count |
---|---|
33 | |
13 | |
9 | |
9 | |
5 |