In Episode 281, we introduced Microsoft OneLake with a high-level overview. Now we're going deeper with a discussion on the Parquet format, why Microsoft went with the Delta Lake variation, and what Delta Lake format brings to the table (no pun intended). We'll also examine some "behind the scenes" aspects of file management, and why you'll still be using the GUI to create most of your objects. Onelake is Microsoft's solution to the demand for centralizing all data in one location, eliminating the need to transfer it across multiple systems. We expect this to play out further however, when we consider scenarios like data sovereignty, geographical data distribution, separation of subsidiary data, and even departmental budgets that may necessitate multiple instances of OneLake. We round out our OneLake deep dive with a conversation on the Direct Lake Mode option for importing data into Power BI and Eugene shares his perspective on why everyone may not be rushing to jump on the bandwagon just yet. We hope you enjoyed this deep dive into Microsoft OneLake! If you have questions or comments, please send them our way. We would love to answer your questions on a future episode. Leave us a comment and some love ❤️ on LinkedIn, X, Facebook, or Instagram. The show notes for today's episode can be found at Episode 282: OneLake - A Deep Dive. Have fun on the SQL Trail!

Ask this episode

“What did the council decide on item 42?” — answered with the speaker and the moment.

Transcript

Related