# Database Migration A software development practice for versioning and applying changes to an application's database schema. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Percona and HexaCluster: Faster, Safer Oracle Migration DevFeed: [Percona and HexaCluster: Faster, Safer Oracle Migration]() Original publisher: [Read original article]() Author: Percona Team Published: 2026-09-14T22:19:16Z Content type: article Language: en Sources: [Blog - Percona]() Topics: [Oracle Database](), [migration](), [Open Source](), [PostgreSQL](), [Database Migration](), [Replication](), [Tooling]() Tags: [database](), [database-migration](), [database-trends](), [engineering](), [insight-for-dbas](), [insight-for-developers](), [migration](), [open-source](), [oracle](), [partners](), [percona](), [postgresql](), [replication](), [schema](), [sql](), [tooling](), [validation]() ### AI overview Percona and HexaCluster describe a partnership for moving organizations from Oracle, SQL Server, DB2, and Sybase ASE to supported open source databases, primarily PostgreSQL. HexaCluster provides assessment and migration engineering through DMAT and HexaRocket, while Percona provides distributions, operators, and long-term support. HexaRocket combines schema migration, data migration, validation, change data capture, live replication, and reverse replication in one platform. ### Source excerpt Percona and HexaCluster have partnered to remove the hardest part of an open source database migration: getting off Oracle, SQL Server, DB2 or Sybase ASE with confidence, on a predictable timeline, without a multi-year consulting program. Percona brings open source expertise, its own distributions, operators and enterprise support. HexaCluster brings the assessment and migration engineering ... Continued The post Percona and HexaCluster: Faster, Safer Oracle Migration appeared first on Percona. ## Jellyfin 12.0 Is Out: What Breaks Before You Upgrade DevFeed: [Jellyfin 12.0 Is Out: What Breaks Before You Upgrade]() Original publisher: [Read original article]() Author: Christian Rakoot Published: 2026-09-08T06:32:10Z Content type: article Language: en Sources: [Self Host Lab]() Topics: [Database Migration](), [Database](), [Security](), [Server]() Tags: [article](), [backup](), [bug](), [data](), [database](), [jellyfin](), [jellyfin-12-0-is](), [jellyfin-news](), [news](), [release](), [security](), [server](), [update]() ### AI overview Jellyfin 12.0 introduces a new versioning scheme and a database rewrite that makes upgrading a consequential operation. Users must meet the supported upgrade path, back up and verify restoration of their configuration and database, complete a full library scan, remove or recompile third-party plugins, and account for removed legacy API and login support. ### Source excerpt Jellyfin 12.0 shipped on September 7, 2026, after months stuck in release candidate limbo. It's the biggest Jellyfin release since the project forked from Emby in 2018, and the version number itself is the first clue: this build reports as 12.0, not 10.12.0. That's not a typo. Jellyfin has dropped the "10" major prefix that led its version numbers since the fork. ## SQL Server to Aurora PostgreSQL conversion with AI agents for AWS DMS DevFeed: [SQL Server to Aurora PostgreSQL conversion with AI agents for AWS DMS]() Original publisher: [Read original article]() Author: Mayur Aggarwal Published: 2026-09-01T15:19:13Z Content type: tutorial Language: en Sources: [AWS Database Blog]() Topics: [AWS Database Migration Service](), [sql-server](), [Database Migration](), [Model Context Protocol](), [Databases]() Tags: [advanced-300](), [ai-agents](), [amazon-aurora](), [aws-database-migration-service](), [database-migration](), [how-to](), [mcp](), [postgresql](), [technical-how-to]() ### AI overview Tutorial on using AI agents with AWS DMS Schema Conversion to convert SQL Server schemas to Aurora PostgreSQL through natural-language workflows. ### Source excerpt Learn how to use AI agents with AWS DMS Schema Conversion to orchestrate SQL Server to Amazon Aurora PostgreSQL schema conversion through natural language. See how the conversion engine processes T-SQL, how the agent drives the workflow, and how to interpret and resolve CRITICAL action items using decision frameworks for common incompatibilities. ## Navigating the Walled Gardens of PostgreSQL: Hidden Risks of Postgres Vendor Lock-in DevFeed: [Navigating the Walled Gardens of PostgreSQL: Hidden Risks of Postgres Vendor Lock-in]() Original publisher: [Read original article]() Author: Robert Bernier Published: 2026-08-26T14:07:50Z Content type: opinion Language: en Sources: [Blog - Percona]() Topics: [PostgreSQL](), [vendor lock-in](), [Database Migration](), [Open Source]() Tags: [database-migration](), [database-trends](), [insight-for-dbas](), [insight-for-developers](), [migration](), [open-source](), [postgres](), [postgresql](), [vendor-lock-in]() ### AI overview The article examines how commercial ecosystems built around PostgreSQL can create walled-garden effects and constrain the portability of PostgreSQL-compatible systems. It highlights migration complexity, switching costs, and potential data-integrity risks when leaving such ecosystems. ### Source excerpt These days there's been a lot of talk about Postgres having an impact on "everything". Whether it's replacing legacy systems, creating a new greenfield project or even implementing it as a back-end to an agentic AI, Postgres is today's poster child for innovation. So performing something as dull and straightforward as a database migration should ... Continued The post Navigating the Walled Gardens of PostgreSQL: Hidden Risks of Postgres Vendor Lock-in appeared first on Percona. ## Deploy Apps and Database Migrations in One CD Pipeline DevFeed: [Deploy Apps and Database Migrations in One CD Pipeline]() Original publisher: [Read original article]() Author: Animesh Pathak Published: 2026-08-05T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [CI/CD](), [Database Migration](), [Deployment](), [Databases](), [DevOps]() Tags: [ci-cd](), [database](), [deployment](), [devops](), [governance](), [migrations](), [pipeline](), [visibility]() ### AI overview The article explains how Harness CD and Database DevOps can combine application deployments and database schema migrations in one CI/CD pipeline. It describes how this unified workflow can improve release consistency, visibility, governance, verification, and rollback safety while reducing deployment risk and operational overhead. ### Source excerpt Learn how Harness CD and Database DevOps automate application deployments and database schema migrations in a unified CI/CD pipeline. | Blog ## What Matters Most for NoSQL Migrations DevFeed: [What Matters Most for NoSQL Migrations]() Original publisher: [Read original article]() Author: Cynthia Dunlop Published: 2026-07-21T13:44:46Z Content type: tutorial Language: en Sources: [ScyllaDB]() Topics: [NoSQL](), [Database Migration](), [migration](), [data-architecture](), [data](), [App]() Tags: [apps](), [community](), [complexity](), [data](), [data-modeling](), [database](), [database-migration](), [databases](), [how-to](), [migration](), [offline](), [performance](), [scale](), [validation](), [what-matters]() ### AI overview This article presents practical guidance for planning, executing, and de-risking NoSQL database migrations. It compares online and offline approaches and emphasizes schema migration, data movement, and validation, with attention to performance, scale, complexity, and disruption. ### Source excerpt How to prioritize the things that matter most for planning, executing and de-risking your NoSQL database migration ## Why Database DevOps Matters in Modern Software Delivery DevFeed: [Why Database DevOps Matters in Modern Software Delivery]() Original publisher: [Read original article]() Author: Jesse Wang Published: 2026-07-17T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [Databases](), [Infrastructure as code](), [DevOps](), [Database Migration](), [iac-security](), [Provisioning](), [Platform Engineering](), [Terraform](), [AWS CloudFormation]() Tags: [aws-cloudformation](), [database](), [deployment](), [devops](), [infrastructure](), [infrastructure-as-code](), [migrations](), [platform-engineering](), [software-delivery](), [terraform]() ### AI overview The article explains that Infrastructure as Code improved infrastructure provisioning but did not address database schema change delivery. It argues that separating infrastructure, application, and database workflows creates operational risk, and presents Database DevOps as a way to bring version control, rollback, and governance to database delivery. ### Source excerpt Infrastructure as Code transformed infrastructure delivery. Learn why database delivery requires a different approach and how Database DevOps closes the gap. | Blog ## Zero Downtime Database Migrations: Safe Schema Changes DevFeed: [Zero Downtime Database Migrations: Safe Schema Changes]() Original publisher: [Read original article]() Author: Animesh Pathak Published: 2026-07-16T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [Database](), [Database Migration](), [migration](), [Availability](), [Code]() Tags: [availability](), [blog](), [compatibility](), [consistency](), [database](), [database-migration](), [learn](), [migrations](), [patterns](), [production](), [schema](), [strategy](), [uptime]() ### AI overview This tutorial explains zero-downtime database migrations through backward-compatible schema changes, the expand-and-contract pattern, dual writes, and phased rollouts. It emphasizes preserving application availability, data consistency, and compatibility while old and new application versions run together. ### Source excerpt Learn zero downtime database migration strategies using backward-compatible schema changes, dual writes, and safe rollout patterns. | Blog ## How to Migrate from SQL Server to PostgreSQL HA for Dockerized Apps DevFeed: [How to Migrate from SQL Server to PostgreSQL HA for Dockerized Apps]() Original publisher: [Read original article]() Author: Jessie Baynas Published: 2026-05-28T07:18:00Z Content type: tutorial Language: en Sources: [SeveralNines]() Topics: [PostgreSQL](), [sql-server](), [migration](), [Database Migration](), [Replication](), [Docker Compose](), [Architecture & Design](), [DevOps](), [Monitoring]() Tags: [cloud-native](), [database-general](), [database-migration](), [deployment](), [devops](), [failover](), [migration](), [monitoring](), [open-source](), [postgresql](), [replication](), [sql-server](), [validation]() ### AI overview This tutorial explains how to migrate a database from Microsoft SQL Server to PostgreSQL for Dockerized applications. It separates schema migration with pgloader from bulk data export using BCP and import with PostgreSQL COPY, and describes a setup involving streaming replication and ClusterControl for deployment, monitoring, and failover. ### Source excerpt For many organizations, migrating from Microsoft SQL Server to PostgreSQL is no longer only about reducing licensing costs. The transition is often part of a broader modernization initiative focused on improving flexibility, scalability, and operational efficiency. PostgreSQL has evolved into one of the most mature open-source database platforms available today. It is widely adopted across [...] The post How to Migrate from SQL Server to PostgreSQL HA for Dockerized Apps appeared first on Severalnines. ## Branching Without Git Is Now The Default DevFeed: [Branching Without Git Is Now The Default]() Original publisher: [Read original article]() Author: Joshen Lim; Qiao Han Published: 2026-05-04T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Databases](), [Database Migration](), [Git](), [GitHub](), [pull-requests](), [Infrastructure as code]() Tags: [ai](), [audit-trail](), [database](), [git](), [github](), [infrastructure-as-code](), [prototyping](), [pull-request]() ### AI overview Supabase has made branching without Git the default for all projects. Developers can create branches from the Supabase Dashboard, edit schemas with the SQL or Table Editor, review schema differences, and merge without configuring GitHub. Git-based branching remains fully supported for teams that manage migrations in version control and use pull request workflows. ### Source excerpt Branching without Git is now the default for all Supabase projects. ## Evolving Database Schemas Without Breaking Production DevFeed: [Evolving Database Schemas Without Breaking Production]() Original publisher: [Read original article]() Author: Raul Junco Published: 2026-03-14T11:57:59Z Content type: tutorial Language: en Sources: [System Design Classroom]() Topics: [Databases](), [Database Migration](), [Refactoring](), [Development]() Tags: [architecture](), [database](), [database-migration](), [databases](), [development](), [refactoring]() ### AI overview The article explains why database refactoring is riskier than code refactoring because multiple applications, dashboards, workers, and analytics pipelines may depend on the same schema. It presents the Expand / Contract pattern as a safer way to evolve schemas without breaking running systems and illustrates how non-backwards-compatible changes can cause production failures. ### Source excerpt A practical pattern for evolving database schemas without breaking production ## From MySQL to CockroachDB at Groww: A Staged Production Migration DevFeed: [From MySQL to CockroachDB at Groww: A Staged Production Migration]() Original publisher: [Read original article]() Author: Sourav De,Vittal Pai,Paresh Saraf Published: 2026-03-11T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [migration](), [Database Migration](), [MySQL](), [Replication](), [Concurrency](), [Cloud]() Tags: [architecture](), [cloud](), [cockroachdb](), [concurrency](), [customers](), [data](), [database-migration](), [distributed](), [experience](), [financial](), [india](), [latency](), [migration](), [mysql](), [parallel](), [production](), [replication](), [scale](), [sql](), [strategy]() ### AI overview This article describes Groww's staged production migration from a managed MySQL cloud instance to CockroachDB. It explains how MOLT supported staged data movement, continuous replication, verification, near-zero downtime, limited application changes, and rollback planning. ### Source excerpt Groww is India's #1 stock broker with 16 million active users and $11 billion in market cap. ## Build Checkpoints For Your Agent Using Neon Snapshots DevFeed: [Build Checkpoints For Your Agent Using Neon Snapshots]() Original publisher: [Read original article]() Author: Andre Landgraf Published: 2025-09-16T22:52:22Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [API](), [Database](), [data](), [Serverless](), [Vibe coding](), [Database Migration]() Tags: [agent](), [agentic](), [agents](), [api](), [app](), [architecture](), [backups](), [code](), [coding](), [compare](), [database](), [disaster-recovery](), [feature](), [product](), [rollback](), [serverless](), [snapshots](), [storage](), [vibe-coding]() ### AI overview The article explains how Neon snapshots can provide checkpoints for agent-built applications. Because each checkpoint preserves the application code together with the corresponding database schema and data, users can compare versions and roll back to a consistent state. Neon's API, serverless Postgres architecture, and copy-on-write storage make this approach practical and cost-effective. ### Source excerpt You can now create Neon snapshots via API. This new capability isn't just useful for backups or disaster recovery, but also serves as a powerful building block for one of the most requested features in agentic platforms: versioning (or checkpoints). Neon's snapshots, built on our... ## Using heroku run for Interactive One-Off Dynos on Heroku Fir DevFeed: [Using heroku run for Interactive One-Off Dynos on Heroku Fir]() Original publisher: [Read original article]() Author: Su Glasgo Published: 2025-09-08T21:33:43Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku](), [Command-line interface](), [Database Migration](), [Authentication]() Tags: [cli](), [cloud-infrastructure](), [database-migration](), [dynos](), [engineering](), [fir](), [heroku](), [opentelemetry](), [performance-optimization](), [security](), [troubleshooting]() ### AI overview This article explains how Heroku Fir supports interactive CLI sessions through dedicated one-off dynos. It describes using these isolated dynos for administrative tasks, database migrations, real-time diagnostics, and troubleshooting, with public SSH key authentication required. ### Source excerpt When Production Goes Sideways Imagine this: It's 2 AM, your phone buzzes with an alert, and your dashboards are screaming. Production is down. Sound familiar? An automated health check has failed, and your internal dashboards are showing a spike in errors. You've just pushed a new release that included a critical database schema change, and [...] The post Triage and Fix with Confidence: heroku run and OTel on Heroku Fir appeared first on Heroku. ## Declarative Schemas for Simpler Database Management DevFeed: [Declarative Schemas for Simpler Database Management]() Original publisher: [Read original article]() Author: Qiao Han Published: 2025-04-03T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Database](), [Database Migration](), [migration](), [Supabase](), [Authorization]() Tags: [access-control](), [code](), [database](), [management](), [migration](), [postgres]() ### AI overview Supabase introduces declarative schemas for managing complex database structures. The approach stores the desired database state in centralized, version-controlled files, can generate migration files automatically, and makes schema changes easier to review. The article contrasts this workflow with traditional migrations, especially as schemas grow more complex. ### Source excerpt Simplify managing and maintaining complex database schemas ## Navigating PostgreSQL Locks with Neon and Atlas DevFeed: [Navigating PostgreSQL Locks with Neon and Atlas]() Original publisher: [Read original article]() Author: Rotem Tamir Published: 2025-03-14T18:26:07Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [PostgreSQL](), [Database Migration](), [Database](), [Back end]() Tags: [api](), [backend](), [community](), [cpu](), [database](), [locking](), [migrations](), [performance](), [postgresql](), [schema]() ### AI overview The article explains how PostgreSQL schema migrations can acquire long-running locks and cause production outages. It uses a uniqueness-constraint example and describes creating and validating a unique index before attaching the constraint to reduce blocking. ### Source excerpt As applications evolve, making changes to your database schema is inevitable, whether you're adding indexes to keep performance up with a growing user base or adding new features to an existing product. Most of the time, these schema migrations will go smoothly, but if you're not... ## Vercel Native Integration: Create a Neon Branch Per Preview DevFeed: [Vercel Native Integration: Create a Neon Branch Per Preview]() Original publisher: [Read original article]() Author: Gustavo Salomão Published: 2025-02-20T02:39:53Z Content type: tutorial Language: en Sources: [Blog -- Neon Docs]() Topics: [Vercel](), [Deployment](), [Database](), [Database Migration](), [Testing](), [GitHub](), [Documentation]() Tags: [community](), [database](), [deployment](), [development](), [environment-variables](), [github](), [guide](), [integration](), [migration](), [product](), [testing](), [vercel](), [workflow]() ### AI overview Neon's Native Vercel Integration can automatically create a Neon database branch for each Vercel preview deployment. The article explains how isolated branches prevent pull-request tests from sharing data, how copy-on-write branches avoid manual seed-data setup, how schema migrations can run during deployment, and how to configure the integration for Development, Preview, or Production environments. ### Source excerpt To Vercel users deploying Neon via the Vercel Marketplace: we have good news. You can now use Neon's Native Vercel Integration to automatically create a database branch for each Vercel preview deployment. Check out our docs for a step-by-step guide. Why deploy Neon branches in yo... ## An API to Track Database Schema Changes DevFeed: [An API to Track Database Schema Changes]() Original publisher: [Read original article]() Author: Luis Tavares Published: 2025-01-09T17:08:23Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [API](), [schema-evolution](), [Database Migration](), [Databases](), [Repl.it](), [CI/CD](), [GitHub Actions](), [Artificial Intelligence](), [Large Language Model]() Tags: [agentic](), [api](), [ci-cd](), [database](), [github](), [github-action](), [llms](), [migration](), [postgres](), [product](), [schema-evolution]() ### AI overview The article introduces the compare_schema API endpoint for Neon's Schema Diff feature. It explains how the API compares schemas between Neon databases and supports CI/CD automation, agentic systems, database migrations, and schema evolution, including use cases involving Replit Agent and Postgres. ### Source excerpt We keep expanding our Schema Diff feature, this time adding an API endpoint: compare_schema. You can use it in all your Neon projects, including the Free Plan. Schema Diff allows you to easily compare schemas between Neon databases. It was first made available via the Neon Consol... ## Planning Your PostgreSQL Migration: Best Practices and Key Considerations DevFeed: [Planning Your PostgreSQL Migration: Best Practices and Key Considerations]() Original publisher: [Read original article]() Author: Ken W. Alger Published: 2024-11-19T19:40:49Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [migration](), [PostgreSQL](), [Database Migration](), [Cloud](), [vendor lock-in](), [interoperability]() Tags: [cli](), [cloud](), [compatibility](), [configuration](), [database](), [database-migration](), [developer-tools](), [heroku-postgres](), [interoperability](), [migration](), [postgresql](), [sql](), [uncategorized](), [vendor-lock-in]() ### AI overview This guide explains how to plan a PostgreSQL migration between cloud providers. It covers evaluating the current database setup, checking PostgreSQL version and extension compatibility, and documenting configuration settings before migration. ### Source excerpt Your organization may have many reasons to move a cloud service from one provider to another. Maybe you've found a better performance-versus-cost balance elsewhere. Maybe you're trying to avoid vendor lock-in. Whatever your reasons, the convenience and general interoperability of cloud services today put you in the driver's seat. You get to piece together the [...] The post Planning Your PostgreSQL Migration: Best Practices and Key Considerations appeared first on Heroku. ## Looking at How Replit Agent Handles Databases DevFeed: [Looking at How Replit Agent Handles Databases]() Original publisher: [Read original article]() Author: Sam Harrison Published: 2024-11-08T17:59:23Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Repl.it](), [Databases](), [Database Migration](), [PostgreSQL](), [SQLAlchemy](), [Artificial Intelligence](), [Object-relational mapping](), [Flask](), [Python](), [web applications](), [API](), [Front end]() Tags: [agent](), [ai](), [api](), [applications](), [code](), [database-migration](), [databases](), [development](), [flask](), [frontend](), [html](), [javascript](), [orm](), [postgresql](), [product](), [python](), [sqlalchemy](), [web](), [web-applications]() ### AI overview This article examines how Replit Agent uses natural-language prompts and AI to build and evolve a full-stack TODO application. It focuses on coordinating Flask, SQLAlchemy, Alembic migrations, and a managed Neon PostgreSQL database while updating the API, schema, and frontend together. ### Source excerpt Replit Agent is a powerful tool within the Replit development environment that allows you to offload coding tasks using natural language and AI. By interacting with the Replit Agent, you can generate code, create applications, and modify existing features simply by asking for wha... ## Database migrations with Geni and libSQL DevFeed: [Database migrations with Geni and libSQL]() Original publisher: [Read original article]() Author: Jamie Barton Published: 2024-08-05T00:00:00Z Content type: tutorial Language: en Sources: [Turso Blog]() Topics: [Database Migration](), [libSQL](), [Turso](), [SQL](), [Command-line interface](), [GitHub Actions]() Tags: [ci-cd](), [cli](), [database](), [database-migration](), [how-to](), [libsql](), [sql](), [turso]() ### AI overview This tutorial explains how to use Geni, a lightweight migration tool, with libSQL and Turso. It covers defining migrations in SQL files, applying and rolling them back through the CLI, using transactions, checking migration status, and automating migrations with GitHub Actions. ### Source excerpt Learn how to use Geni to manage your database migrations. ## Build with confidence with Schema Diff & Protected Branches DevFeed: [Build with confidence with Schema Diff & Protected Branches]() Original publisher: [Read original article]() Author: Raouf Chebri Published: 2024-04-16T13:33:07Z Content type: tutorial Language: en Sources: [Blog -- Neon Docs]() Topics: [Database](), [protected branches](), [Structured-data](), [Development](), [Database Migration](), [Tooling]() Tags: [code-review](), [collaboration](), [community](), [database](), [debugging](), [development](), [postgres](), [protected-branches](), [schema](), [serverless]() ### AI overview Neon's article introduces schema diff and protected branches for Neon database branching. It explains how schema diff compares a branch's current and past schemas, including its use in debugging, code review, and collaboration, and demonstrates the feature in the Neon Console. ### Source excerpt Neon helps teams ship with confidence without compromising development velocity. One of its features that contributes to that is database branching. In this post, we will explore two new features related to database branching: schema diff and protected branches. Database branches... ## 3 common foreign key mistakes (and how to avoid them) DevFeed: [3 common foreign key mistakes (and how to avoid them)]() Original publisher: [Read original article]() Author: Charlie Custer Published: 2023-06-28T00:00:00Z Content type: tutorial Language: en Sources: [Cockroach Labs]() Topics: [Databases](), [Database Migration](), [CockroachDB](), [data](), [SQLite]() Tags: [3](), [cockroachdb](), [data-type](), [database](), [errors](), [how-to](), [mistakes](), [schema](), [sql](), [sqlite](), [systems](), [types]() ### AI overview This tutorial explains three common foreign key mistakes: mismatched data types, dangling references to nonexistent tables or columns, and related schema problems. It describes how these issues can arise and how to prevent them, including database-specific behavior in SQLite and CockroachDB. ### Source excerpt Foreign keys are an important element of any relational database. But when you're setting up your database schema, it's relatively easy to create problems for yourself if the foreign keys aren't set up correctly. Here are three of the most common mistakes made with foreign keys, and a little advice on how to avoid them! ## Database migrations made easy with Atlas DevFeed: [Database migrations made easy with Atlas]() Original publisher: [Read original article]() Author: Glauber Costa Published: 2023-06-06T00:00:00Z Content type: tutorial Language: en Sources: [Turso Blog]() Topics: [Database Migration](), [Databases](), [Turso](), [SQLite]() Tags: [database-migration](), [databases](), [software-development](), [sqlite](), [turso]() ### AI overview The article presents database migrations as changes to a database schema needed to accommodate new or updated data, and introduces Atlas as a way to make migrations easier. The supplied text also provides historical context about an older version of Turso and its SQLite-based architecture. ### Source excerpt Database migrations is one of the thorniest subjects there is. In short, they happen when a database schema must change to accommodate new or updated data. One simple example of a database migration... [Next page]()