Пікірлер

• 
  @PatrickFlynn-hl5gg2 ай бұрын

  By far the best introduction to Fabric I have seen. Cuts out the marketing fluff and covers real design insights.

• 
  @denisoko84942 ай бұрын

  Hi James, Thanks for this video, it complies well with my thoughts. FYI I had or have all 3 Mesh Types in different productions. Mesh Type 1 uniformity and centralization is good to start fast from scratch as a Data Mesh core. Mesh Type 2 distribution and its domain and storage total uniformity are too optimistic for real life and have limited application. Mesh Type 3 is too agile and diverse, so it may introduce a high total cost of ownership if it is selected as a core for Data Mesh, however, if there is a hybrid cloud, 3rd party SaaS API, a custom HPC cluster, a "good enough" legacy system, or security/privacy constraints IMHO it is reasonable to use Mesh Type 1 as a core and combine it with Mesh Type 3 plugins, where each Mesh Type 3 plugin mimics Mesh Type 1 approach for its input and output data products. I prefer using Mesh Type 1 + 3 as it offers centralized control, cost-efficiency, and fast development. This is achieved by utilizing the Mesh Type 1 core as a default and having the flexibility to extend the core with diverse Mesh Type 3 domain plugins, giving us agile capability.

• 
  @jamserra2 ай бұрын

  Hi Denis...thanks for the feedback! I'll definitely expand on the 3 mesh types in my book for the next edition 🙂

• 
  @sanishthomas28582 ай бұрын

  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

• 
  @jamserra2 ай бұрын

  Thanks for the kind words Sanish!

• 
  @imsushantjain3 ай бұрын

  kzread.info/dash/bejne/iI2hzKyeYsq4YaQ.html Unity Catalog in Databricks has solved the RLS and Column Masking. A very impressive and interesting video. For me it served a good recap :) Cheers Thank You

• 
  @hamedsahami3 ай бұрын

  I work as a data engineer in Snapp Group in Iran. I recently read your book and I want to thank you for your wonderful book. The contents of your book were very close to my experiences in recent years and I enjoyed the events.

• 
  @jamserra3 ай бұрын

  Thanks for the kind words Hamed!

• 
  @GAND3RSON4 ай бұрын

  Great video, finally understand what this

• 
  @NeumsFor95 ай бұрын

  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? 🤣

• 
  @tomfontanella65855 ай бұрын

  Nicely explained! Thanks

• 
  @user-im6ij1ct3i5 ай бұрын

  That was a great explanation. Thanks for this.

• 
  @andrasgal316 ай бұрын

  Crystal clear explanation.

• 
  @tyronefrielinghaus34676 ай бұрын

  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.

• 
  @jamserra6 ай бұрын

  Glad you found it helpful!

• 
  @mehmetoz8866 ай бұрын

  Thank you sir, it's now much way more clear.

• 
  @rossgh766 ай бұрын

  Thank you for the amazing video..

• 
  @user-rw7hp5jn9g6 ай бұрын

  I want to say a big thank you for incredibly useful and easy explanations. Well done.

• 
  @jamserra6 ай бұрын

  Thanks for the kind comment!

• 
  @leerunnels71667 ай бұрын

  my ex husband Vincent is not doing very well now. I still love him very much. Please if you see this keep him in your prayers. Lee Runnels

• 
  @Lukas_blck8 ай бұрын

  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?

• 
  @jamserra8 ай бұрын

  It does come down to Spark vs T-SQL, which Spark usually faster for transforming data

• 
  @eliaszeray79818 ай бұрын

  Great! Thank u.

• 
  @malcolm37798 ай бұрын

  💃 "Promo SM"

• 
  @informationcounter19838 ай бұрын

  Huge regrets for not finding this video earlier. The best have seen so far. yesterday got your book from O'Reilly. Spent night reading it and all I can say that such book and subject was very much required. thank you very much James. Have started following you on LinkedIn.

• 
  @cternove8 ай бұрын

  “things i like behind me” for some reason i thought to myself he likes printers 😂 … jk this is a great video Thank you!

• 
  @Anbu_Sampath9 ай бұрын

  Nice talk to understand the high-level how all connected together and compare with existing offering.

• 
  @lakshmisrinivaskiran10379 ай бұрын

  Amazing way of explaining with granular details. Thanks

• 
  @aretez95019 ай бұрын

  Thanks for the explanation. It's really helpful.

• 
  @terryliu36359 ай бұрын

  Great intro video!! Fully agree on the comment regarding dedicated SQL pool!! We made a touch but wise decision to stay away from it for new analytics projects kicked off at the beginning of this year!!

• 
  @user-im6ij1ct3i10 ай бұрын

  Great Presentation , thank you

• 
  @risebyliftingothers10 ай бұрын

  BY FAR THE SINGLE MOST EFFECTIVE EXPLANATION EVER ❤

• 
  @risebyliftingothers10 ай бұрын

  BY FAR THE SINGLE MOST EFFECTIVE EXPLANATION EVER ❤

• 
  @user-lj8fc8ug8h10 ай бұрын

  How can I get access to the links on the presentation?

• 
  @alt-enter23710 ай бұрын

  This was incredibly helpful! I am prepping to teach the DP-500 and one of the things I am trying to figure out is how to compare/contrast/talk about "traditional" Synapse vs. Fabric. Your insights really help!

• 
  @vibhaskashyap824710 ай бұрын

  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

• 
  @DavidZebrowitz10 ай бұрын

  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..

• 
  @vt145411 ай бұрын

  Finally, I understood the whole buzz around Fabric. Main differentiators from Synapse look like SaaS | OneLake | Dropping MPP aka Dedicated Pool | Compute/storage decoupling (official) |...plue few more. I am not sure how well "Auto discovery and registration of table" feature will work - specially if metastore already exists in Databricks. Will Databricks share its metastore with Fabric or we will recreate metastore here? Also, will metastore be at workspace level or tenant level?

• 
  @DanielWillen11 ай бұрын

  If you were to create a shortcut to a CSV file , right now it seems that you have to manually create the table, and it does not update if the source file changes. It's quite common that we have folders in the datalake containing versions of a csv. Sales_01 , Sales_02 etc. In serverless sql you could just target them with openrowset and an asterisk. Sales_* would just load all the files in the folder. And since it was a view you would always gaurantee the data was not stale. Are there plans to improve the way data is loaded as tables in the lakehouse to support this?

• 
  @tomchelle111 ай бұрын

  as an old-school EDW guy, you cut through much of the terminology fuzziness and answered several questions I had. Thank you

• 
  @tyronefrielinghaus34676 ай бұрын

  Yup : the terminology fuzziness ...source of soooo much confusion, and ''wrong thinking"

• 
  @devyaninair279311 ай бұрын

  Thanks for a simple yet insightful session

• 
  @jplee12311 ай бұрын

  Great video! Can you please post the links in your Data Mesh section (46:37) or the presentation as a whole? Thanks.

• 
  @jamserra11 ай бұрын

  Glad you like it! I posted the deck link in the description.

• 
  @williamrodriguez542611 ай бұрын

  Great overview! Thankful for the 'Azure-Translation' (i.e., showing how all the products fit into the overall data flow)!

• 
  @loganathannainar480411 ай бұрын

  good explanation, thank you

• 
  @7777linpaws Жыл бұрын

  Does MS Fabric supports things like Private connections to on-prem, key vaulted credentials/configs like Azure does? Is it something we can expect to see in future if not there already?

• 
  @f27tzn Жыл бұрын

  That was as clear as you could get. Thanks for the great work!

• 
  @thomasgauchet6470 Жыл бұрын

  very clear! Thank you James

• 
  @AlistairCreenz Жыл бұрын

  Thanks for this, it was very helpful. Showing the sql endpoint on the lakehouse editor was a revelation.

• 
  @Irmon88 Жыл бұрын

  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.

• 
  @kipmadden8952 Жыл бұрын

  As always, you break down what has been a source of confusion with clarity - Thanks!

• 
  @jamserra Жыл бұрын

  Thanks for the kind words!

• 
  @sababag1 Жыл бұрын

  Hi Great content - Why not to use both Warehouse and Lakehouse? for example DataBricks that uses Lakehouse and AWS-RDS for Warehouse

• 
  @Nilsp14 Жыл бұрын

  Hi James, first of all, great video! Most of our current dashboards are built on Tableau which connects to our SQL database. If we moved to Fabric and used OneLake, would we still be able to connect to Tableau?

• 
  @jamserra Жыл бұрын

  Yes, Tableau can pull in data from OneLake, since the data in OneLake is stored in delta format, which Tableau can read

• 
  @thomasgremm6127 Жыл бұрын

  Hi James, thanks for the good introduction! Good insights into the architecture of Fabric/OneLake. Will it be possible to use data virtualization as a layer between on-premise SQL Server 2022 and OneLake (maybe, in conjunction with the new feature Shortcuts). I remind myself, that SQL Server 2022 is able to use the Polybase v3 feature in conjunction with ADLSv2 access (virtually), but since OneLake is somehow extra/segregated from ADLSv2, I doubt that it will be possible, at the moment. A workaround for me would be to data virtualize between on-premise and ADLSv2, and then shortcut/"bridge over logically" to OneLake (hosted in Fabric capacity). Thanks in advance!

• 
  @jamserra Жыл бұрын

  Hi Thomas, I expect you will eventually see Synapse link integrated into Fabric. Synapse Link supports data virtualization to SQL Server 2022. Your workaround will do in the meantime 🙂

• 
  @leerunnels7166 Жыл бұрын

  6:39

• 
  @leerunnels7166 Жыл бұрын

  Am still with Vincent. Love him so much.

• 
  @keen8five Жыл бұрын

  kzread.info/dash/bejne/k2p1lcytpqWcYrg.html "Do not [...] use Pipelines within Synapse" I hope we are fine as long as we don't use (Synapse) Data Flow activities.

• 
  @jamserra Жыл бұрын

  Hi Martin, I would also avoid using Synapse pipelines and use ADF pipelines instead. This is because there will be a migration tool for ADF pipelines to Fabric much sooner than a migration tool for Synapse pipelines to Fabric

• 
  @vantuandang7761 Жыл бұрын

  Once again, Great and useful video! Thank you James!