Skip to content
  • There are no suggestions because the search field is empty.

LoadControl Options (Project)

Applies to
Platform: Microsoft SQL Server · Snowflake · Databricks · Fabric Lakehouse · Fabric Warehouse · Oracle

LoadControl Options (LoadControlOptions) select how the generated loaders are orchestrated: by a native load control, by Apache Airflow, or both. The generator writes the load-control artifacts for each selected value.

The dbt generators do not offer the property.

Values

A multi-select list in Project Settings. Each platform offers these values, the first one being the default:

  • Microsoft SQL Server, Oracle: Native Load Control, Airflow.
  • Databricks, Fabric Lakehouse: Multi-Threading Notebook, Airflow.
  • Fabric Warehouse: Multi-Threading Notebook.
  • Snowflake: Depending Tasks, Stage-Driven Tasks, Near-Realtime Tasks, Airflow.

Meaning of the values:

Effect on generated output

On Microsoft SQL Server, Native Load Control adds the load-control scripts and execute.sql. Airflow alone produces only the DAG; deploy.sql then deploys the layers and runs the deployment validation, without load-control scripts. With both values selected, the artifacts contain both.

Example

The Data Vault Test Project on Microsoft SQL Server with Native Load Control and Airflow has these files in LoadControl:

configure_loadcontrol.sql
datavault_mssql_dag.py
deploy_loadcontrol.sql
L000_Loadcontrol_Deployment.sql
L010_Stage_Configuration.sql
L020_Raw Vault_Configuration.sql
L030_Business Vault_Configuration.sql
LoadControl_Execution_Datavault.Mssql.sql

Related articles