This guide walks you through creating and configuring Azure Databricks Jobs to orchestrate multiple notebooks, define task dependencies, execute Dimension and Fact table pipelines, create a master orchestration job, and schedule automated daily execution.
By completing this guide, you will:
Daily Scheduler
│
▼
Master Orchestration Job
│
┌───────────┴───────────┐
▼ ▼
Daily Refresh DIM Daily Refresh FACT
│ │
▼ ▼
Bronze → Silver → Gold Bronze → Silver → Gold
│ │
└───────────┬───────────┘
▼
Analytics Ready Tables
Before creating Databricks Jobs, ensure you have:
Navigate to:
Jobs & Pipelines
└── Create
└── Job
Provide a meaningful Job Name.
Example:
daily_refresh_dim

Inside the Job page click
Notebook
This creates the first task for your workflow.

Configure the notebook task.
| Property | Value |
|---|---|
| Type | Notebook |
| Source | Workspace |
| Compute | Serverless |
Click
Path
Browse to your notebook.

Browse through the Workspace folders.
Example:
Workspace
└── 02_bronze
└── dimension_tables
└── 01_ingest_dimensions
Click
Confirm

Configure the notebook task.
| Property | Value |
|---|---|
| Task Name | dime_bronze |
| Notebook Path | 02_bronze/dimension_tables/01_ingest_dimensions |
| Compute | Serverless |
Click
Create Task

Click
Add Task
Add additional notebooks.
Example workflow:
Configure task dependencies so each notebook starts only after the required upstream task succeeds.

After configuring all notebook tasks, the workflow should resemble a complete dependency graph.
Example execution flow:
Bronze
│
▼
Silver Common Utilities
│
├── Brand
├── Category
├── Product
├── Customer
└── Calendar
│
▼
Gold Common Utilities
│
├── Product
├── Customer
└── Calendar

Click
Run Now
Databricks executes every task according to the configured dependencies.
The Timeline view displays:

Create another Job.
Example:
daily_refresh_fact
Add notebook tasks for Fact processing.
Example tasks:
If required, configure Job Parameters such as:
| Parameter | Example |
|---|---|
| catalog_name | ecommerce |
| storage_account_name | storageaccount001 |
| container_name | ecom-raw-data |

Create one more Job.
Example:
daily_refresh
Instead of Notebook tasks, add
Run Job
tasks.
Add:
Configure the Fact Job to depend on successful completion of the Dimension Job.
Execution Flow:
Daily Refresh DIM
│
▼
Daily Refresh FACT

The completed orchestration should contain two Job tasks.
Run_Daily_Refresh_Dim_Job
│
▼
Run_Daily_Refresh_Fact_Job
This allows one master Job to execute the complete ETL workflow.

Open
Schedules & Triggers
Click
Add Trigger
Configure:
| Property | Value |
|---|---|
| Trigger Type | Scheduled |
| Schedule Type | Schedule |
| Frequency | Every Day |
| Time | 02:00 |
| Time Zone | Asia/Calcutta (UTC +05:30) |
Click
Save

After saving, the trigger appears under
Schedules & Triggers
Your pipeline will now execute automatically every day according to the configured schedule.

Daily Scheduler
│
▼
Master Job
│
├──────────────► Daily Refresh DIM
│ │
│ ▼
│ Bronze Layer
│ │
│ ▼
│ Silver Layer
│ │
│ ▼
│ Gold Layer
│
▼
Daily Refresh FACT
│
▼
Bronze Layer
│
▼
Silver Layer
│
▼
Gold Layer
│
▼
Daily Summary
| Job | Naming Pattern |
|---|---|
| Dimension Job | daily_refresh_dim |
| Fact Job | daily_refresh_fact |
| Master Job | daily_refresh |
| Bronze Tasks | Bronze_ |
| Silver Tasks | Silver_ |
| Gold Tasks | Gold_ |