Running Models
Learn how to compile, run, and test your dbt models in dbdeux. Execute from the IDE, the DAG Explorer, or let scheduled jobs handle it automatically.
Run Modes
dbdeux supports all standard dbt execution modes:
| Mode | Command | What it does |
|---|---|---|
| Run | dbt run | Builds models in your warehouse (creates tables/views) |
| Test | dbt test | Executes data tests and reports pass/fail results |
| Build | dbt build | Runs models then tests them (recommended for most workflows) |
| Compile | dbt compile | Resolves Jinja and shows final SQL without executing anything |
| Seed | dbt seed | Loads CSV seed files into your warehouse |
| Snapshot | dbt snapshot | Captures slowly changing dimension snapshots |
Running from the IDE
Single Model
- Open a model file (e.g.,
models/staging/stg_orders.sql) - Click the Run button in the toolbar, or press
Cmd/Ctrl + Enter - Choose the run mode from the dropdown
- Results appear in the output panel below the editor
Multiple Models with Selectors
Use the command bar to run with dbt selector syntax:
# Run a single model
stg_orders
# Run a model and everything downstream
stg_orders+
# Run everything upstream of a model (ensure dependencies are fresh)
+dim_customers
# Run all models in a folder
staging.*
# Run models by tag
tag:daily
# Run modified models (compared to production)
state:modified+
# Combine selectors
staging.* tag:critical
Run with Full Refresh
For incremental models, force a full rebuild:
- Click the dropdown arrow next to Run
- Select Run with Full Refresh
- The model rebuilds from scratch instead of incrementally
Running from the DAG Explorer
A visual way to select and run models:
- Open the DAG Explorer
- Click on any model node
- In the context panel, choose:
- Run: Execute just this model
- Run with upstream: Ensure all parent models are fresh first
- Run with downstream: Also rebuild everything that depends on this model
- Optionally select multiple nodes by holding
Shiftand clicking
Viewing Results
After a run completes, the results panel shows:
Run Summary
- Status: Success, failure, or error
- Duration: Total execution time
- Models affected: Count of models that were built
- Row counts: Number of rows created in each model (where available)
Per-Model Results
Click any model in the results to see:
- Execution duration for that specific model
- Row count (for table materializations)
- Compiled SQL that was executed
- Any warnings or errors
Test Results
When running tests (via test or build mode):
- Green checkmarks for passing tests
- Red indicators for failures with the specific failing rows
- Click a failure to see the query that returned unexpected results
- Jump directly to the model or test definition to fix issues
Logs
The Logs tab shows the full dbt output, including:
- Compilation messages
- Execution progress for each model
- Error traces for debugging
- Timing information
Run History
Access the history of all runs for your project:
- Navigate to Runs in the sidebar
- Filter by status, user, date range, or model
- Compare run durations over time
- Re-run any historical run with the same configuration
Tips and Best Practices
- Use Build mode for most development work (catches both model and test failures)
- Compile first when working on complex Jinja logic to verify the output SQL
- Use selectors to avoid running your entire project every time
- Check the DAG before running downstream models to understand the full impact
- Review Schema Diff after runs to confirm expected schema changes