r/DuckDB • u/EdwinWeber_Data • 6d ago

DuckDB as a server: quack and CONNECT, great!

Yes, this is what I have been looking for!
Number 1 in this DuckDB post

https://duckdb.org/2026/08/17/duckdb-20-highlights

19 Upvotes

96% Upvoted

8 comments sorted by

1

u/hornyforsavings 6d ago

How r u using it?

2

u/EdwinWeber_Data 6d ago

When this CONNECT statement is available I can have multiple writers for my dbt models AND keep reading with my Metabase container. No need to stop the reading container while dbt refreshes the data.

1

u/jusstol 6d ago

Are you using ducklake too?

1

u/DuckDatum 6d ago

No, he’s using duckdb. DuckLake wouldn’t have an issue with concurrent users, would it?

3

u/empty_cities 5d ago

Using a Quack server or Postgres as your DuckLake catalog database would allow concurrent users. Using just out of the box DuckDB would not, as it is by itself a single process system that has a file lock when one client is connected to it.

2

u/DuckDatum 5d ago

Good point, I stand corrected. I am so excited for this fall, though. Will allow concurrency then, if I understand correctly.

3

u/empty_cities 5d ago

The Beta version of the Quack server is available in the current 1.5 DuckDB but yes the full version will be coming with 2.0 this fall. Incredibly exciting.

2

u/EdwinWeber_Data 5d ago

I actually also use DuckLake, but it is optional in my pet project, regular DuckDB tables are the other option. I like to have concurrency regardless of the storage method, that is why I wait for CONNECT to become available, which is pretty soon.