Yes, that WAS a very clear presentation : I really was confused between L and Ws. He anticipated my question of why the 2 instead of just one. We need the behind the scenes details (like this) to grok what is going on.
Awesome content which not only explain the technical nuances but also explain the use case of Lakehouse versus Warehouse from the architecture design perspective. Enjoyed watching video and got lots of clarity. Thanks James
Thank you! I was thinking that the Warehouse was more like a dedicated pool. I'm hoping it is a bit more robust than the current Synapse Serverless.. at least once we get more T-SQL support..
Excellent content. I've been using Synapse for a while and it took me sometime to get through all the different options and limitations. This video helps clarifying a lot about Fabric. Can't wait for the book to be published. Thank you.
Hi, thanks for the great content! in terms of performance of querying and transforming data, which of the two is preferred? Or does it come down to comparing Spark vs T-SQL?
Great information on this video. I have seen so many other channel and video saying bla bla about the Fabric but this video looks the most informative. guys like and subscribe for this effort
End of the day, new warehouse FEELS almost like the serverless sql endpoint with the ability to also now write data with T-SQL in a DEFAULT DELTA format + the Polaris engine + the ability to use Snowflake like cloning to make test environments a lot easier in the same way Juan Soto should make things easier for the Yankees? 🤣
as an old-school EDW guy, you cut through much of the terminology fuzziness and answered several questions I had. Thank you
Yup : the terminology fuzziness ...source of soooo much confusion, and ''wrong thinking"
Yes, that WAS a very clear presentation : I really was confused between L and Ws. He anticipated my question of why the 2 instead of just one. We need the behind the scenes details (like this) to grok what is going on.
Glad you found it helpful!
Awesome content which not only explain the technical nuances but also explain the use case of Lakehouse versus Warehouse from the architecture design perspective. Enjoyed watching video and got lots of clarity. Thanks James
Thank you! I was thinking that the Warehouse was more like a dedicated pool. I'm hoping it is a bit more robust than the current Synapse Serverless.. at least once we get more T-SQL support..
Excellent content. I've been using Synapse for a while and it took me sometime to get through all the different options and limitations. This video helps clarifying a lot about Fabric. Can't wait for the book to be published. Thank you.
Hi, thanks for the great content! in terms of performance of querying and transforming data, which of the two is preferred? Or does it come down to comparing Spark vs T-SQL?
It does come down to Spark vs T-SQL, which Spark usually faster for transforming data
Thanks for this, it was very helpful. Showing the sql endpoint on the lakehouse editor was a revelation.
As always, you break down what has been a source of confusion with clarity - Thanks!
Thanks for the kind words!
That was as clear as you could get. Thanks for the great work!
Hi Great content - Why not to use both Warehouse and Lakehouse? for example DataBricks that uses Lakehouse and AWS-RDS for Warehouse
That was a great explanation. Thanks for this.
Thanks for the explanation. It's really helpful.
very clear! Thank you James
Great information on this video. I have seen so many other channel and video saying bla bla about the Fabric but this video looks the most informative. guys like and subscribe for this effort
Thanks for the kind words Sanish!
good explanation, thank you
End of the day, new warehouse FEELS almost like the serverless sql endpoint with the ability to also now write data with T-SQL in a DEFAULT DELTA format + the Polaris engine + the ability to use Snowflake like cloning to make test environments a lot easier in the same way Juan Soto should make things easier for the Yankees? 🤣