texlytics

Loading

Category Microsoft Fabric

24/07/ 2026
The Dedupe Key That Doesn’t Drift

This article was originally published on LinkedIn and is archived here on texlytics.com. There is a reflex every data engineer has when they need to deduplicate rows: hash the row, compare the hashes, keep one of each. It is fast, it is simple, and on a well-behaved source it is correct. I reached for it without thinking when I built the ingestion for one of our CMiC AP voucher endpoints. It was the wrong call, and the way it failed is worth writing down, because the lesson holds…

Read more
10/07/ 2026
The Most Important Table in My Microsoft Fabric Environment

This article was originally published on LinkedIn and is archived here on texlytics.com. Most data engineers love talking about pipelines. Others love talking about notebooks, Spark, semantic models, or dashboards. But after building a near-real-time Microsoft Fabric integration framework that ingests dozens of CMiC endpoints every fifteen minutes, I’ve come to a different conclusion: The most important object in my entire environment isn’t a pipeline. It’s a table. Not a fact table.Not a dimension table.A control table. What started as a simple metadata repository evolved into the operational…

Read more
26/06/ 2026
Stop Writing One Pipeline Per Source

This article was originally published on LinkedIn and is archived here on texlytics.com. Every data engineer hits this moment. You’ve integrated three systems, you’re proud of it, and then a fourth source shows up. So you do what you did the last three times: copy the previous notebook, find-and-replace the table names, tweak the date logic, adjust the pagination, ship it. It works. You now have four notebooks that are 80% identical and 20% subtly different — and that 20% is where every future bug will live. Then…

Read more