That old SSIS package reading Dynamics 365 is one more reason the SSIS server can't be switched off. BimlFlex reads Dynamics 365 as a native source via the ADF Dynamics linked service. Define it once in metadata and generate the ADF pipeline instead of porting the package.

Strict means declaring the shape you expect. Flipping mergeSchema off declares nothing. In BimlFlex, one Databricks source object can carry a declared schema and FAILFAST while the rest of the landing layer stays forgiving. varigence.com/blog/databrick…

Half of tonight's partner files are missing a required column. The merged read fills those rows with NULL, and the load still goes green. A partial break is the expensive kind. Here's how to enforce one Databricks feed without tightening the rest. varigence.com/blog/databrick…

Dynamics 365 data still coming through an aging SSIS package nobody touches when a field is added? BimlFlex generates the Data Factory load from metadata, many-to-many included. The package you babysit becomes a pipeline you regenerate. varigence.com/bimlflex?utm_s…

BimlExpress on a machine with no internet? Offline keys are a separate flow from the web key request. Start with the machine code: in VS Code, let the extension fully start, then click Get Machine Code in the BimlExpress sidebar. Generate the key at varigence.com/account?utm_so…

A partner's best design travels to client number two. Lakeflow Designer keeps adding canvas diffs and operator lineage, but the design stays on one client's canvas. BimlFlex keeps your patterns in metadata you reuse. Each client gets native notebooks and SQL in its own Git.

Hand-editing linked services in the portal each release is how a dev connection string reaches prod. Each BimlFlex build writes an ARM template and parameters file for your Data Factory, plus a PowerShell deploy script. Promotion is a parameter change. varigence.com/bimlflex?utm_s…

Hey Data Vault teams: trace a key column upstream in BimlFlex Model Lineage and each column argument of its FlexToBk or FlexToHash expression shows up as its own key hop. The record source token @@rs is dropped, since it isn't a column. varigence.com/blog/column-li…

Hey BimlExpress users: the Biml you run on your laptop can build on a server too. BimlStudio's command-line compiler runs headless with response files, --ddlBuildMode and --buildDocumentation, so one CI step builds the packages, the DDL and the docs. varigence.com/bimlstudio?utm…

History should be a choice you can show an auditor, not a table that survived because nobody truncated it. In BimlFlex, the PersistHistory connection setting makes persistent staging a historized bronze layer or a current-state ODS. One flip, regenerate. varigence.com/bimlflex?utm_s…

Release week, and the only person who knows how to configure the SSIS Catalog project is out. BimlFlex builds Catalog-ready packages headless, Project or Package model, and every build writes its own deploy scripts. Nobody has to remember the steps. varigence.com/bimlflex?utm_s…

A link says a customer and an account were related. It doesn't say when that stopped being true. In BimlFlex, you mark the Driving Key and effective-date columns in metadata, and the link effectivity loads are generated from there. varigence.com/bimlflex?utm_s…

Two columns share a name, so a tool draws a lineage line between them. That line is an inference. BimlFlex Model Lineage labels it name match, beside the hops labeled mapping or key. And where it finds no evidence at all, it draws no line. varigence.com/blog/column-li…

the warehouse is sized xl because someone had one slow query in march. the query got fixed in april. nobody has been brave enough to touch the dial since, and at this point the dial is part of the architecture.

act one: we'll tag every cloud resource by team act two: the biggest line on the bill is tagged "test" act three: "test" has been in production since 2023

Add an attribute to a satellite and every hand-coded hashdiff column list has to change with it. Miss one and change detection skips it, no error. BimlFlex generates the hashdiff from the model, so the column list can't fall out of step. varigence.com/blog/what-a-da…

Anyone who hand-mapped Dynamics 365 many-to-many relationships knows the slow part: finding the bridge entity. BimlFlex's native Dynamics linked service for ADF (Dynamics CRM or Dynamics 365) resolves it through the IntersectEntity. varigence.com/bimlflex?utm_s…

SSIS shops don't have to become Spark shops overnight to land on Databricks. What carries a migration is the patterns: staging, change detection, restartable loads, audit columns. A well-run SSIS estate already has them. Notebook syntax is the easy part.

Query five satellites as of one date and you're writing date-range joins, unless someone built the PIT table. BimlFlex generates Point-in-Time tables as rolling date windows, maintained incrementally, and Bridge tables with a Zero Record by default. varigence.com/blog/data-vaul…

Most stacks write a column's precision down twice: in the DDL and in the load code. Eventually they disagree. BimlFlex keeps each column's type, length, precision and scale in metadata. Synapse DDL and Databricks code both generate from it, so they can't disagree.