Scaling up to down fabric capacity giving utilisation error.
Hello, I have upscale my fabric capacity to F32 from F8 because I want to process 400 gb of data so now I have completed my work on few minutes and then I have down scale fabric capacity from F32 to F8 but after scaling down it is giving error like your organization has used entire capacity no capacity available. How to resolve this i don't want to increase capacity to resolve this issue.Fabric Notebook for Power BI Developer by Sandeep Pawar
Microsoft Fabric has a number of notebook options available. In this session, we will review how to use these notebooks, the differences between them and how it can help Power BI developers to create and manage Power BI datasets and reports effectively. TENTATIVE AGENDA (subject to change, all times listed are in Pacific Time): 5:45pm Teams Meeting opens 6:00pm-7:05pm Welcome 6:05pm-6:05pm Feature Presentation 6:05pm-7:10pm Wrap-up REGISTRATION: This meet-up will be hosted on Microsoft Teams and will be recorded for those who cannot attend live. To access the Teams Meeting link, you must RSVP for the event. JOINING THE EVENT: Attendees can join the Teams Meeting starting at 5:45 pm PST on the day of the event. The link will be visible only if you RSVP beforehand. The event will begin at 4:00 pm PST. Please ensure you are on mute to minimize background noise and distractions. During the presentation, type your questions and comments into the chat area, which will be monitored by the event hosts. There will be a Q&A session at the end, where you can unmute your mic and share your video to ask questions.Data Connect: Introduction to Notebook in Microsoft Fabric
Indore Data & BI Community (IDBC) presents: Data Connect Series Join us for another exciting session where we explore "Introduction to Notebooks in Microsoft Fabric" with Bhanu Gautam, a Microsoft Super User. Date: 12th April 2025 Time: 11:00 AM IST Venue: Online What You’ll Learn? Introduction to Notebooks in Microsoft Fabric How to leverage Python & Spark for data engineering Working with Lakehouse & Dataflows using Notebooks Best practices & real-world applications Speaker: Bhanu Gautam | Microsoft Super User Host: Anmol Malviya | Microsoft Super User Who Should Attend? Data professionals, Power BI users, and tech enthusiasts Those interested in Microsoft Fabric & data engineering Anyone looking to enhance their Notebook & Spark skills Let’s learn, collaborate & innovate together! Register Now Join IDBC on Microsoft Teams: https://teams.live.com/l/community/FEAPg7Z13cnL8RrVAU Join Our WhatsApp Group for Updates: https://chat.whatsapp.com/HL6aOLHMqAGJm1JqpzhkJw
Bayesian Thinking for Data Science in Microsoft Fabric
In this edition, we’re exploring Bayesian modeling and how to think about uncertainty in a more realistic, practical way using PyMC3. By the time you’re done, you’ll have a clear intuition for what Bayesian thinking really means, why it’s so useful in day-to-day data work, and how it changes the way you interpret results. We’ll also explore how PyMC3 supports this mindset in a structured but approachable way.
Materialized Lake View - 'Invalid Date, Invalid Date'
Recently started seeing some very strange behaviour following updating my OPDG to the August release where if we add or remove a column from a materialized lake view, other columns become 'Invalid Date, Invalid Date'. For example we dropped 'age' from a people table, and the unchanged 'title' column turned to this: The column is clearly a string and the SQL sat behind this runs as expected (column populated Mr/Mrs/etc). We rolled back to the previous OPDG in a hope it was something to do with that as its been working fine and the update is the only thing that happened around the time we noticied the issue - but rolling back hasn't helped. We update the MLV when needed by dropping it, and then creating a new one, so it shouldn't be holding any ghost data types or anything weird. We've even dropped a MLV, gone on lunch, and ran the create when we got back thinking maybe it took a bit to propogate the drop.. but at this point it feels like we're clutching.. it also didnt work and we got the same issue. It does this on any MLV, from any data source. recreation: CREATE MATERIALIZED LAKE VIEW IF NOT EXISTS `silver-ws`.silver_lh.core.people AS... (SQL..) -> DROP MATERIALIZED LAKE VIEW IF EXISTS `silver-ws`.silver_lh.core.people; -> CREATE MATERIALIZED LAKE VIEW IF NOT EXISTS `silver-ws`.silver_lh.core.people AS... (change the SQL giving a new column or removing an existing one) -> fields are messed up. Anyone come across this before, or have any insight as to what the reason might be?Choosing the Right Way to Run Python in Microsoft Fabric
Fabric gives us several ways to run Python, and at first they can look overlapping. In this post, I share the practical decision model I use to choose the right option based on execution mode, compute engine, and data access path. If you are code-first and want fewer wrong turns when moving from exploration to production, this guide is for you.Causal Inference for Data Science in Microsoft Fabric
In this edition, we’re exploring into causal inference and why it matters once you move beyond basic reporting and prediction. By the time you’re done, you’ll have a clear understanding of how causal thinking differs from traditional analytics and how to reframe everyday business questions around cause and effect instead of simple correlation. And because insights only matter if they’re understood, we’ll look at how to communicate causal findings clearly and responsibly so decision-makers know what they can trust and act on.
