# DataGrip 2026.3 joins data across different databases using embedded DuckDB

JetBrains' new Workspace data source lets developers join tables from separate database connections in one SQL query without setting up a separate query server. It is an initial implementation with optimisation limits.

DataGrip 2026.3 embeds DuckDB to run cross-database joins over existing connections, reducing ad hoc data export and ETL setup.

- Status: Active
- Published: 2026-11-12T19:49:01+13:00
- Updated: 2026-11-12T19:49:01+13:00
- Categories: Web Development, Cloud & Infrastructure, Developer Tools, Databases & Storage
- Tags: databases, DuckDB, JetBrains
- Canonical HTML: https://beyondthe.news/dossiers/datagrip-2026-3-duckdb-cross-database-workspace-queries

## What changed

JetBrains DataGrip 2026.3 introduced a per-project Workspace data source backed by in-memory DuckDB. It runs SQL across existing database connections, including different DBMSs, and returns joined results directly in the IDE. The release also adds first-class DuckDB syntax and connection support.

## Why it matters

Builders who need to compare production-adjacent datasets across PostgreSQL, MySQL or other sources can perform exploratory joins without standing up Trino, copying tables to an intermediate server or writing one-off export scripts. This reduces setup friction, not the need to control credentials, data movement and query costs.

## How the Workspace works

Each DataGrip project can create one Workspace data source and multiple query consoles. A special qualified table-reference syntax selects tables from existing data-source connections; embedded DuckDB executes the cross-source query. The Workspace is in memory by default and does not require a persistent DuckDB file.

## Why DuckDB was selected

JetBrains considered Apache Calcite and internal query handling before selecting DuckDB custom table functions. The team says they allowed it to reuse existing query execution and obtain some optimisation capabilities without building a query engine. This is a vendor/implementer account, not an independent benchmark.

## Operational boundaries

The feature uses DuckDB SQL dialect, which may differ from the SQL supported by connected systems. Cross-source reads can move data between sources and the local IDE process; teams should check permissions, network transfer, memory limits, sensitive data handling and query plans before treating this as a production data pipeline.

## First release, not a federated database replacement

JetBrains calls this an initial solution. Further optimiser integration and file-based data sources are prospective rather than shipped capabilities. No independent performance or large-dataset reliability benchmarks were established.

## Key details

- Released as part of DataGrip 2026.3 in November 2026.
- One in-memory DuckDB Workspace data source per project.
- Queries can join tables from different configured DBMS connections.
- DuckDB SQL dialect and native DuckDB connection support included.
- JetBrains says optimiser and file-source integration will evolve.

## Builder takeaways

- Try Workspace queries for one-off cross-system investigation before building ETL.
- Use read-only credentials and test with non-sensitive datasets.
- Check query plans, memory use and data-transfer costs for large joins.
- Do not assume transactional consistency across separate databases.

## What to watch

- Cross-source query pushdown and optimisation improvements.
- Independent large-dataset performance and failure testing.
- Expansion to file-based sources and additional supported connectors.

## Uncertainties

- No independent cross-database performance benchmark located.
- Exact pushdown and connector limitations vary by backend.
- Workspace is not a cross-system transactional consistency mechanism.

## Sources

- [What's New in DataGrip 2026.3](https://www.jetbrains.com/datagrip/whatsnew/) — JetBrains · primary · 2026-11-06T00:00:00+13:00. Feature release and usage details.
- [Cross-database queries](https://www.jetbrains.com/help/datagrip/cross-database-queries.html) — JetBrains Documentation · primary · 2026-11-06T00:00:00+13:00. Workspace semantics and query setup.
- [How JetBrains Built Cross-Database Queries into DataGrip with DuckDB](https://www.duckdb.org/2026/11/05/jetbrains-datagrip) — DuckDB · secondary · 2026-11-05T00:00:00+13:00. Interview with JetBrains engineers about design alternatives and first-version limits.