SUPPORTED DATABASES
The rule is simple: every engine that both dbt and Sling support is a DVT adapter — dbt runs your default-target models, Sling moves data during federation. Anything outside that intersection is reached through Python models instead.
FULL ADAPTER SUPPORT (PUSHDOWN + EXTRACTION + TARGET)
| DATABASE | TYPE | STATUS |
|---|---|---|
| PostgreSQL | postgres | ✓ verified |
| Snowflake | snowflake | ✓ verified |
| BigQuery | bigquery | supported |
| Redshift | redshift | supported |
| Databricks | databricks | ✓ verified |
| MySQL | mysql | ✓ verified |
| MariaDB | mariadb | ✓ verified |
| SQL Server | sqlserver | ✓ verified |
| Oracle | oracle | ✓ verified |
| DuckDB | duckdb | ✓ verified |
| Microsoft Fabric | fabric | supported |
| ClickHouse | clickhouse | ✓ verified |
| Trino | trino | ✓ verified |
| SQLite | sqlite | ✓ verified |
| Amazon Athena | athena | supported |
PYTHON MODEL SOURCES
No dbt+Sling adapter needed — Python models run locally and land results in your DAG. Python models guide.
REST APIsMongoDBElasticsearchStarRocksExcel / local filesML inference
SLING-ONLY CONNECTORS (SOURCE + FILE TARGET)
No dbt adapter — these work as extraction sources for federated models, and as bucket-style targets (results land as files).
SFTP
BUCKET STORAGES (SOURCE + TARGET)
Use cloud buckets or local filesystem as extraction sources or materialization targets. Data moves via Sling, compute runs in DuckDB.
| STORAGE | TYPE | KEY FIELDS |
|---|---|---|
| Amazon S3 | s3 | bucket, region, access_key_id, secret_access_key |
| Google Cloud Storage | gcs | bucket, project_id, keyfile |
| Azure Blob Storage | azure | account, container, access_key |
| Local Filesystem | filesystem | path |
Full bucket storages guide — profiles.yml setup, source/target examples, incremental extraction, supported formats.
FILE FORMATS
| FORMAT | READ | WRITE |
|---|---|---|
| CSV | ✓ | ✓ |
| Parquet | ✓ | ✓ |
| JSON / JSONL | ✓ | ✓ |
| Delta Lake | ✓ | ✓ |
| Avro | ✓ | ✓ |
| Excel (XLSX) | ✓ | — |
| IPC/Arrow | ✓ | ✓ |