O Refresh de Ontem Ainda Está Cobrando
O Refresh de Ontem Ainda Está Cobrando
Episode 37 • 2026-10-16 Duration: 10:24
Fabric não cobra quando o trabalho acontece — distribui o custo por 2.880 intervalos de trinta segundos. Essa frase explica todo comportamento confuso de capacity, inclusive por que surge protection pode rejeitar o SQL que deveria proteger.
What we discuss
- How it actually works underneath the abstraction
- Where the obvious answer breaks
- A real Reddit/Microsoft Q&A question unpacked
- F-SKU realism — what this actually costs
- When the rejected approach is actually right
- Risks of the recommended path
- The architectural principle to take home
Key takeaways
- E alguém está prestes a cortar o SKU pela metade porque o gráfico parece calmo.
- O pico que eles veem é um recibo. A linha suavizada é a conta que ainda não chegou.
- Agora mesmo, em algum lugar, tem um gráfico de capacity com uma noite de cara tranquila.
Watch the episode
The Fabric Friday video on this topic: https://youtu.be/iE-jdcseCaY
From the video
- 7:42 Demo: Watch One Job Spread
- 9:51 The Throttling Staircase, and Who Skips Steps
- 2:50 Demo: Read the Metrics App
- 12:46 Sizing From the Smoothed Line
Resources
- Fabric capacity throttling policy
- Smoothing and throttling in Fabric Data Warehouse
- Throttle triggers and throttle stages
- Capacity planning guide
- Autoscale Billing for Spark
- Fabric operations: interactive and background
- Understand the metrics app timepoint page
- Understand the metrics app timepoint summary page
- Surge protection
- Capacity and SKUs
- Burstable capacity in Fabric Data Warehouse
- Consumption rates and billing for Copilot in Fabric
- Azure quotas for Fabric capacities
About the show
AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.
Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.
Submit your case
Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.
Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.
Brand design based on fabricperiodictable.com.