Varigence

Hand-assembling Databricks deployment files? BimlFlex generates warehouse code from metadata. Configured to run processing in Databricks, it emits an Asset Bundle, a deployment file set with databricks.yml and resource YAML. Add environment details, review, then deploy.

Client five shouldn't mean install five. BimlFlex keeps every client's warehouse model, and every version of it, side by side in one metadata database you host. The next release starts with Clone Version, which copies the current model, not the server.

One source needs one setting changed. The usual fix is a copy of the whole pattern, and now you maintain two. BimlFlex lets you override that setting for one batch, project, connection, object or column, and warns when an override would change nothing.

An int fits until it doesn't. BimlFlex generates warehouse code from metadata. Data type mappings, rules for destination types, can make int → bigint a house standard where mappings apply. Give growing values room in the destination.

Moving to Databricks shouldn't put a SQL team on call for Python at 3am. BimlFlex generates your Databricks staging, Data Vault and mart code from one model, and one setting, DatabricksUseSqlScripting, makes it SQL.

Before changing warehouse metadata, keep a way back. BimlFlex, a metadata-driven warehouse code generator, can capture and restore solution metadata with snapshots. Recovery of the warehouse data needs its own plan.

Every in-house framework has a settings table and one person who knows what the columns mean. In BimlFlex, each setting that shapes the generated code shows its description, default and where its value came from. Ones your platform ignores stay hidden.

The first weeks of a Data Vault project go to hand-drawing hubs and links from source schemas you already have. Import them, run the BimlFlex Accelerator, and one click generates Hubs, Links and Satellites. Hashing is a setting: SHA1, MD5, SHA2. varigence.com/blog/data-vaul…

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…