settings.sql

Execution settings — how the runtime uses DuckDB

Phase: Pre-catalog | Order: 1 | Required: No

OndatraSQL runs directly on DuckDB. This file controls how the runtime executes queries — memory usage, parallelism, and disk spill behavior.

You usually don’t need to change this. Defaults work for most cases.

-- Limit how much memory the runtime can use
SET memory_limit = '8GB';

-- Control parallel execution
SET threads = 4;

-- Where to spill when memory is exceeded
SET temp_directory = '/tmp/duckdb';

-- Timestamp interpretation
SET TimeZone = 'Europe/Stockholm';

This file runs before the DuckLake catalog is attached.

Common Settings

Most projects never change these. Adjust only if needed.

Setting	What it controls	When to change
`memory_limit`	Max memory used by the runtime	Large datasets or limited RAM
`threads`	Parallel execution	Limit CPU on shared machines
`temp_directory`	Disk spill location	Slow disks or constrained environments
`TimeZone`	Timestamp interpretation	Working across regions

For advanced tuning, see the DuckDB configuration reference.