data-integrity-guardian

To check database migration scripts for data loss and privacy compliance, review them for reversibility, transaction handling, and PII encryption. This process identifies potential data loss, integrity violations, and GDPR privacy risks before deployment.

Ensuring referential integrity during a database migration involves checking cascade behaviors, foreign key relationships, and dependent associations. This prevents orphaned records and verifies that business rules and data constraints are properly enforced.

Validating ACID properties and transaction boundaries in SQL scripts requires assessing atomic operations, isolation levels, and deadlock scenarios. Proper review ensures robust rollback handling and prevents integrity violations during execution.

You need to review data models for GDPR compliance and PII encryption whenever persistent data code handles personal information. This identifies sensitive data, verifies encryption standards, and checks retention policies to ensure regulatory compliance.

Yes, this data integrity review is designed for production database management. It assesses migration safety by identifying potential data loss scenarios and integrity violations, ensuring safe updates like adding new columns and updating records.

Your database migration script risks orphaned records and deadlocks due to improper transaction boundaries and missing foreign key constraints. Reviewing cascade behaviors, isolation levels, and rollback handling resolves these referential integrity issues.