About Database Schema Validator

Validate database schemas for naming conventions and best practices. Part of the DevTools Surf developer suite. Browse more tools in the Developer Utilities collection.

Use Cases

• Review a database schema before migration to catch consistency issues early
• Enforce naming conventions across a team's database design
• Validate schema changes in CI before applying to staging or production
• Audit legacy schemas for normalization violations and technical debt

Tips

• Paste CREATE TABLE statements for the entire schema — the validator checks cross-table consistency including foreign key references to non-existent tables
• Use the naming convention mode to enforce snake_case, table prefix, or column naming standards across your entire schema
• The normalization analysis identifies columns that violate 1NF (multi-valued), 2NF (partial dependencies), or 3NF (transitive dependencies) with explanations

Fun Facts

• Database normalization was formalized by E.F. Codd in a series of papers from 1970-1974, introducing first through third normal forms. Boyce-Codd Normal Form (BCNF) was later developed by Codd and Raymond Boyce in 1974 as a stronger version of 3NF.
• The term 'denormalization' refers to intentionally violating normal forms to improve query performance — adding redundant columns, pre-computed aggregates, or flattened structures. Modern analytical databases (Redshift, BigQuery, Snowflake) routinely use denormalized schemas (star schema, wide tables) for performance.
• PostgreSQL enforces schema constraints (NOT NULL, UNIQUE, CHECK, FOREIGN KEY) with ACID guarantees — meaning the database itself rejects invalid data rather than relying on application code. This is called 'database as a gatekeeper' and prevents entire classes of data integrity bugs.

FAQ

What is the difference between a schema and a database?

In PostgreSQL, a schema is a namespace within a database that contains tables, views, and functions. One database can have multiple schemas (default: 'public'). In MySQL, 'schema' and 'database' are synonymous. The term is used loosely to mean 'the structure of your tables.'

Should I use foreign key constraints?

Yes for OLTP databases — they prevent orphaned records and enforce referential integrity at the database level. Some high-scale systems disable FK constraints for insert performance, enforcing referential integrity at the application level instead — a tradeoff requiring careful discipline.

What is third normal form (3NF)?

A table is in 3NF if: every non-key column depends on the primary key, the whole key, and nothing but the key. The classic violation: storing a customer's city and also their zip code, where city depends on zip (a transitive dependency). Splitting into a separate zip-code table resolves this.