Overview Quickstart dbt Compatibility The Style Guide profiles.yml sources.yml Configuration Supported Databases

SQLITE

Serverless, file-based relational database. Ideal for local development, testing, and embedded analytics.

DVT SUPPORT

✓ FEDERATION SOURCE

read in federation models

✓ FEDERATION TARGET

materialize federation results

✓ DEFAULT TARGET

run full dbt projects against it

✓ SEED TARGET

dvt seed --target loads here

DVT supports SQLitebecause both dbt and Sling do: dbt drives standard materializations when it's your default target, Sling moves data in and out during federation. Connectivity for both layers is checked with dvt debug --all.

PREREQUISITES

Driver: sqlite3 — installed automatically by:

dvt sync

CONFIGURATION FIELDS

FIELD	TYPE	REQUIRED	DEFAULT	DESCRIPTION
type	string	yes	—	Must be `sqlite`
path	string	yes	—	Path to SQLite database file
threads	integer	no	1	Number of parallel threads

PROFILES.YML EXAMPLE

my_project:
  target: sqlite_dev
  outputs:
    sqlite_dev:
      type: sqlite
      path: ./local.db

SOURCES.YML EXAMPLE

sources:
  - name: local_data
    meta:
      connection: sqlite_dev
    tables:
      - name: users
      - name: transactions

DBT ADAPTER FEATURES

When SQLite is your default target, every standard dbt model runs through the official dbt adapter — all of its documented capabilities apply unchanged:

MATERIALIZATIONS

INCREMENTAL STRATEGIES

NOTABLE CONFIGS

▸file-path databases (absolute paths recommended)

Official dbt SQLite adapter docs ↗

FEDERATION INCREMENTAL STRATEGIES

Strategies available when this engine is the target of a f_incremental model:

✓ Append✓ Delete+Insert✓ Merge

KNOWN LIMITATIONS

⚠Single-user — file locks prevent concurrent writes
⚠No network protocol — file must be locally accessible