Survey

Database changes are risky — especially in growing teams.
A junior dev can rename/drop a column, CI passes, deployment succeeds, and production silently breaks (dashboards wrong, queries slow, billing off).

Today this is handled by:

• Senior engineers manually reviewing SQL

• Tribal knowledge

• Post-deploy monitoring (too late)

Existing tools

• Migration tools (Liquibase/Flyway) → execute changes safely

• Observability tools → detect issues after prod breaks
  
  I am trying to validate if there exists a tool which can solve this problem.
  Looking for feedback and what I am doing wrong or what more can be done