Optimize Warehouse costs with capacity pause and resume

Welcome back to another episode of Fabric Espresso DW series. In this episode, we'll be exploring capacity pause and resume features so you can minimize costs and maximize efficiency.
🎙 Meet the Speakers:
👤 Guest from Microsoft Fabric Product Group: Sowmya Sivaraman is a Senior Product Manager on the Microsoft Fabric (Data Warehouse) team, owning experiences like billing, pause/resume, cost monitoring and other user consumption experiences via SQL Query editor.
LinkedIn: / sowmyasivaraman
👤 Host: Filip Popović is a Senior Product Manager at Microsoft and part of the Fabric Product Group, focusing on performance. Before joining Microsoft in 2019, he spent over ten years in the software and financial services industry, delivering business analytics solutions using the Microsoft technology stack.
LinkedIn: / popovicfilip
Twitter: / filippop_msft
👍 Like this video? Don't forget to hit the 'Like' button and share it with your network!
🔔 Stay Updated: For more insights into Microsoft Fabric Data Warehousing, and all things tech, make sure to subscribe to our channel and hit the notification bell so you never miss an episode!
#Microsoft #MicrosoftFabric #FabricWarehouse

[@Milhouse77BS]

Looking forward to this.

[@bitips]

Question : If I'm playing separately for storage, why my storage becomes inaccessible when my capacity is paused ?

[@up_0078]

Data is accessible as long as you have compute available. You create databricks cluster or any other compute and can access data stored on onelake.

[@04mdsimps]

I tried fabric last summer when it came out and deemed it a beta at that point. Now its a year on, why should I move from azure synapse and power bi to fabric?