serverpod-migrations

Serverpod database migrations are generated by detecting changes to tables, fields, relations, or indexes in your `.spy.yaml` models and creating the corresponding SQL migration files. You can trigger this using the `serverpod` MCP tool during development.

The best way to apply Serverpod migrations during production deployment is by starting the server with the `dart run bin/main.dart --apply-migrations` command. This ensures your database schema stays in sync when the server launches.

To repair an inconsistent Serverpod database, generate a repair migration using the `serverpod create-repair-migration` command, then apply it by restarting the server with the `--apply-repair-migration` CLI flag.

Yes, Serverpod generates SQL migrations automatically from your ORM models. When you modify `table` definitions in your `.spy.yaml` files, it derives the necessary SQL schema changes to prevent drift.

You should skip Serverpod migration operations when no database is configured for your application. The migration workflow is only necessary when your project relies on a database to store its data.

Schema drift occurs when `.spy.yaml` model changes are not translated into applied SQL migrations. Prevent broken deployments by generating migrations from your model updates and applying them via the MCP tool or server startup command.