or go to full-text search page →

Search

Search IconIcon to open search

Every Database Migration is One Too Many

Last updatedUpdated: by Simon Späti · CreatedCreated: · 2 min read · growing Note status Growing. Worked on quite a bit, still rough. Expect bullets, gaps and views that update. Estimated from edit history · 2 sessions over 1 day · 237 words · How my notes grow Recent changes 5 weeks ago +4 / −0 words 5 weeks ago published · 192 words

How many times have I had to migrate from Microsoft SQL to Oracle or to any other database, or switch the Cloud Data Warehouse or Cloud Providers, sometimes for reasons, and sometimes just because management decided so.

Mostly, one Data Migration is one too many. This also counts for Open Data Stacks, or for data pipelines from one framework to the other or to change language. But on the other hand, these are real-life events we can’t fully avoid, especially if tools and companies get acquired.

I’d say one more database migration, or tool migration, is one too many 🙂. There’s a lot of SQL Transpiler that can convert from one dialect to the other. There’s even a transpiler for semantic layer specifications conversion with Apache Ossie. However, the time to do so, and to make sure every edge case is still working as part of the ETL pipeline or in the dashboard, is not as simple as “LLM migrate”, unfortunately, but for sure it helps.

# Read More


Origin: Data Migration, later: Discussio on LinkedIn
Category: Data Lakes & Table Formats
References: Excel Never Dies