September 28, 2026

What Is Data Warehouse Automation?

A working definition with the artifacts to back it: the same batch generated for SSIS, Azure Data Factory and Databricks, the run log every step writes, and a three-question checklist for judging tools.

September 4, 2026

One Failure, Two Recoveries

A failed load leaves one recovery flag in the BimlCatalog you own. The next run reads that flag and does the strongest thing its runtime supports: a generated rollback container on SSIS, a clean re-execute on ADF.

August 28, 2026

The Pipeline That Knows Its Limits

How BimlFlex prices every load by the activities it needs, packs generated sub-pipelines against a configurable budget, chains the overflow, and fails the build with a clear message instead of failing your deployment.

August 12, 2026

Lineage You Didn't Have to Declare

After each successful batch, BimlCatalog reads the timing of the last two successful runs and records which package finished right before each one started. See the mechanism, its limits, and the query that reads the result back.

July 29, 2026

Your Databricks Job Graph Is YAML You Own

Each batch in your model becomes a generated job file where solve-order groups run as chained sub-jobs and per-object thread numbers decide what runs in parallel. The dependency logic lives in YAML you can read, diff, and version.

July 3, 2026

Don't Rewrite SSIS. Read It.

Modernize SSIS without liquidating it. BimlFlex reads your existing DTSX packages and regenerates them forward to ADF, Fabric, or Databricks, so you keep the business logic and drop the rewrite.