Jordan T.

This is really cool. Thanks for sharing!

Just wanted to chime in and say that yes, Azure blob storage support is coming to DuckDB, but also, if your query engine and your storage are in different clouds, you’re going to have a bad time. Egress costs are ~80/TB. This is probably an order of magnitude higher than you’d spend on processing. (consider BigQuery is $6/TB). This can be reasonable for one time data movement, but not recommended for your main data lake. The exception if CloudFlare R2, you can store in R2 without egress costs.

Hi Timo... just wanted to chime in and say that we prioritized getting the EU region up and running first and didn't have time to build migration tooling; we also weren't certain how many people would want to migrate. We have written this doc which should hopefully help by going in a bit more detail.

Also if you're interested in DuckLake, I'm giving a talk today in Andy Pavlo's seminar series "Future Data Systems" More info here

Hi Lars! MotherDuck is very excited about DuckLake, and our goals are primarily:

Some key things that are in the upcoming roadmap:

If you have more specific questions happy to answer.

Awesome, great to hear!

One option is to use the COPY FROM DATABASE (SCHEMA) command COPY FROM DATABASE db1 TO db2 (SCHEMA); which will copy only the schema and not the data. (not sure if this works in place or not, or whether you’d need to copy to a dummy database first)

Awesome, looking forward to seeing the differences. We have reshaped the instances a bit, but also duckdb has made some improvements, so it will be interesting to see the outcomes. (also IIRC we had you on XL instances most of last year which had a bit more memory than our current jumbos)