database

Plan safe database schema migrations by generating forward DDL and rollback SQL with rationale for index and constraint decisions. Validate data integrity, document deployment risk, and ensure changes are traceable and reversible.

A database migration deployment risk assessment should include backfill strategy, validation steps for production readiness, and measurable rollback procedures. Document these alongside forward and rollback DDL to ensure changes are traceable and reversible.

Design database schema changes without breaking data integrity by applying normalization rules, validating constraints, and indexing decisions. Read the current schema state before proposing changes to ensure robust database design.

Yes, you can use this approach for PostgreSQL migration planning. It guides you through schema design reviews, performance considerations, and forward and rollback SQL generation specifically tailored for PostgreSQL database environments.

The best way to document database schema state before a migration is to maintain a DATABASE.md file. Read the current schema from this file to understand the state before proposing changes and generating migration plans.

You need a backfill strategy for database migrations when schema changes require existing data to be populated or transformed. Include backfill logic in your migration plan alongside deployment risk assessment and validation steps for production readiness.