Schema Evolution: Surviving the Day Upstream Renames a Column
Every source schema changes eventually. Which changes Delta accepts silently, which it rejects, a contract per layer, and the changes no schema check sees.
Thoughts on data engineering, cloud architecture, and technology. 2205 articles and counting.
Showing 24 of 2205 posts — page 1 of 92
Every source schema changes eventually. Which changes Delta accepts silently, which it rejects, a contract per layer, and the changes no schema check sees.
Should last year's revenue move when a customer changes segment? Pick an SCD type per column, write a replay-safe Type 2 MERGE, and join facts correctly.
APPROXIMATEDISTINCTCOUNT now runs on Import and Direct Lake models in preview. Decide per measure where about 1.6% error is fine, label it, and test the gain.
Document Intelligence wins on fixed layouts, Content Understanding on variable or multimodal input: split the pipeline and leave stable extractors alone.
Small files come from simple arithmetic, and every reader pays a cost per file. Where they come from, how to measure them, and how to compact them safely.
Fabric's preview data engineering agent runs with the launching engineer's permissions. What to delegate first, which settings to pick, and what stays human.
Microsoft backed Apache Ossie at FabCon with a Power BI converter. It makes metric names portable, not DAX semantics, security rules or performance.
Fabric mirroring for BigQuery is GA, but it moves cost to Google: CDC compute, egress, keyless reseeds and schema ownership decide when to mirror or copy.
Fabric IQ is GA in Copilot Chat, Cowork and MCP. Treat each semantic model as an agent endpoint: RLS, OLS, metadata contracts and default-on access.
DiskANN vector indexes are now GA in Azure SQL and Fabric SQL. When embeddings belong next to your rows, and when Azure AI Search still wins.
A query for one day should not read three years. How partition pruning works, the five ways it silently breaks, and how to pick partition columns.
Foundry routines run an agent on a timer, a schedule or a GitHub or Teams event. When to use them, when to use a workflow, and guardrails for unattended runs.
Foundry's preview egress controls attach ordered destination rules to a hosted agent. Why that limits prompt-injection damage, and how to roll it out safely.
GPT-6 arrived in Foundry ten weeks after GPT-5.6. Pin versions, gate on real queries, shadow traffic and plan retirements before you switch tiers on day one.
The physical plan shows what Spark will actually do: shuffles, join strategy, pruning, Python UDFs. How to read one, and which plans should worry you.
Eventstream can now read Azure Event Hubs with workspace identity. How to move off SAS keys, the RBAC each side needs, and when a service principal still wins.
One hot key can make one task do a third of a job, and more nodes will not help. How to spot skew in the Spark UI, find the keys, and fix it properly.
Power Platform and Dynamics 365 release plans moved to the AI at Work roadmap. Why a CoE now needs continuous change intake, not two planning events a year.
Fabric Data Warehouse GPU query acceleration is in preview. Why the 7x benchmark won't predict your bill, and how to run a fair A/B test on your own queries.
Late data is a distribution you can measure, not an edge case. How to set a waiting policy, handle what arrives after it, and say when a number is final.
Fabric data agents now use GPT-5.1 and a Responses API client. What notebook, Foundry and app callers must change, and why you need a full eval re-run.
Developer mode and PBIP are GA and PBIR becomes the default report format. Why that makes report review realistic, what breaks, and how to stage the move.
Fabric Runtime 2.0 is GA and set to become the default in late September. A plan to inventory, test libraries and Delta features, and pin runtimes first.
Every record has three timestamps: when it happened, when it arrived, and when it was processed. Group by the wrong one and past days keep changing.