I have been reading through many forums and watched videos, but couldn't all required users/item level access information which this video is brought. It is crisp, to the point and clears all understanding very well. thanks for putting the effort to create this.
Thanks for your kind words! I did a video on licensing and costs when Fabric was first released, a few minor details have changed since then so I will probably record an update video soon :) here it is: ruclips.net/video/w481BSXk0Bw/видео.html
Thanks Will for all the efforts you are putting on bringing valuable contents on #Fabric, they are golden and definitely the best channel on that matter from far. I never missed any of your video (thanks to the subscribe) PS : some time ago i thought you gave up since you didn't post any new content for weeks but im happy you're back on track 😉 All the best for your channel and your learning web site, ill sign up for it!
Very kind of you to say Guillaume, thanks! Haha yes I did take a little break, I was working full-time and it was a very busy period in my life. But then I quit that job and now focus 100% on teaching Fabric, so there will be lots more (hopefully high-quality) videos to come. Thanks a lot for your support
Your 7th point also affects Lookup activities too. I might have a work around (possibly) - in the Source there's a field for Lakehouse. If you add the Lakehouse ID (a GUID) into the Dynamic Content section (Click OK), add the correct Workspace ID (Again a GUID) and refresh the 'Tables' section, it might show the tables in that Lakehouse. (it does for me) It's not perfect as it sometimes resets the options if you adjust the Copy Data activity, but I've successfully copied from one workspace to another from a pipeline in a third workspace. Haven't tried it with Stored Procs yet.
... By the way, taking about cross workspace limitations i found a "nice" one recently... step_1 Create a lakehouse L1-EMEA in a Workspace EMEA (Hosted on any EMEA Fabric capacity) then an other Lakehouse L2-APAC from a Workpace APAC (hosted on any APAC Fabric capacity). Step_2 create a Table shortcut from L2-APAC pointing to any tables of L1-EMEA . Step_3 open the L2-APAC and read the shortcuted table with a notebook = all good.....Now open L2-APAC SQL Analytics endpoints or the Default L2 semantic model and you'll see they will be empty 😮..... It's a "cross-workspace/region" scenario limitation that Microsoft is now aware and hopefully will find a solution soon (since this architecture scenario will be rather common for Global companies)
Hello, I have created 3 workspaces dev/test/prod and in each of these workspaces there is bronze/silver/gold lakehouse. This is good and keeps maintainance low. But how can I segregate my data tables in bronze/silver/gold Lakehouse for example sales, product, customer, finance, hr etc ? Is there a way to do it ? Please let me know.
Would be good to call a stored procedure for a data warehouse in another workspace. Could have a central warehouse for auditing, meta data etc which all pipelines used regardless of workspace.
I added an Idea for that, and it is apparently ‘Planned’. You can vote here to give it more urgency ☺️: ideas.fabric.microsoft.com/ideas/idea/?ideaid=b8afba33-2dcf-ee11-92bd-6045bdb0416e
Really useful explanation. Isn't it the OneLake created at tenant level not at the capacity level ? When you create Fabric tenant, then it will create a OneLake which can be used in any capacity created in that tenant.
I have been reading through many forums and watched videos, but couldn't all required users/item level access information which this video is brought. It is crisp, to the point and clears all understanding very well. thanks for putting the effort to create this.
Good to hear that it clarified some things for you! Thanks for watching!
This level of granularity is outstanding. Thank you for the content.
👍 thanks! Yes the details are important for those looking to implement this stuff in the real world!
One of the best channels on data analytics. Is there a video on fabric license costs pls
Thanks for your kind words! I did a video on licensing and costs when Fabric was first released, a few minor details have changed since then so I will probably record an update video soon :) here it is: ruclips.net/video/w481BSXk0Bw/видео.html
Thanks Will for all the efforts you are putting on bringing valuable contents on #Fabric, they are golden and definitely the best channel on that matter from far. I never missed any of your video (thanks to the subscribe) PS : some time ago i thought you gave up since you didn't post any new content for weeks but im happy you're back on track 😉 All the best for your channel and your learning web site, ill sign up for it!
Very kind of you to say Guillaume, thanks! Haha yes I did take a little break, I was working full-time and it was a very busy period in my life. But then I quit that job and now focus 100% on teaching Fabric, so there will be lots more (hopefully high-quality) videos to come. Thanks a lot for your support
Your 7th point also affects Lookup activities too.
I might have a work around (possibly) - in the Source there's a field for Lakehouse. If you add the Lakehouse ID (a GUID) into the Dynamic Content section (Click OK), add the correct Workspace ID (Again a GUID) and refresh the 'Tables' section, it might show the tables in that Lakehouse. (it does for me)
It's not perfect as it sometimes resets the options if you adjust the Copy Data activity, but I've successfully copied from one workspace to another from a pipeline in a third workspace.
Haven't tried it with Stored Procs yet.
Ah nice, thanks for that Steven!
Your content is gold! Thank you so much for sharing these brilliant videos with the community, and please keep it up! :)
Thanks for watching! Glad you're enjoying, lots more in the pipeline :)
... By the way, taking about cross workspace limitations i found a "nice" one recently... step_1 Create a lakehouse L1-EMEA in a Workspace EMEA (Hosted on any EMEA Fabric capacity) then an other Lakehouse L2-APAC from a Workpace APAC (hosted on any APAC Fabric capacity). Step_2 create a Table shortcut from L2-APAC pointing to any tables of L1-EMEA . Step_3 open the L2-APAC and read the shortcuted table with a notebook = all good.....Now open L2-APAC SQL Analytics endpoints or the Default L2 semantic model and you'll see they will be empty 😮..... It's a "cross-workspace/region" scenario limitation that Microsoft is now aware and hopefully will find a solution soon (since this architecture scenario will be rather common for Global companies)
Oooh that is very useful to know, thanks for highlighting that!
Thanks Will for all your effort on this kind of videos! New sub here :) Keep going!
Welcome to the channel, thanks for joining us! I'm glad are enjoying!
Super nice thank you !! Do you have any suggestion about CI/CD pipeline deployment , workspaces automatical creation etc ?
Quite useful information, you got a new subscriber!😎
This is a great presentation, i appreciate a lot, thanks
thanks for watching!
Hello,
I have created 3 workspaces dev/test/prod and in each of these workspaces there is bronze/silver/gold lakehouse.
This is good and keeps maintainance low.
But how can I segregate my data tables in bronze/silver/gold Lakehouse for example sales, product, customer, finance, hr etc ?
Is there a way to do it ?
Please let me know.
Great channel, love your content.
Cheers James, thanks for watching!!
Would be good to call a stored procedure for a data warehouse in another workspace. Could have a central warehouse for auditing, meta data etc which all pipelines used regardless of workspace.
I added an Idea for that, and it is apparently ‘Planned’. You can vote here to give it more urgency ☺️: ideas.fabric.microsoft.com/ideas/idea/?ideaid=b8afba33-2dcf-ee11-92bd-6045bdb0416e
@@LearnMicrosoftFabric will do :)
Golden! Such a great channel:-)
Hey Oskar, really appreciate that man - thanks for commenting! Just getting started!! 😊
Really useful explanation. Isn't it the OneLake created at tenant level not at the capacity level ? When you create Fabric tenant, then it will create a OneLake which can be used in any capacity created in that tenant.
That's correct yes, one OneLake per tenant, which can include multiple capacities
Great video thank you :)
Thanks to you for watching!
Bro are you doing good health wise?
All good thanks bro