Database Schema Designer

Expert guidance on structuring data for scalability, integrity, and performance.

When to Use This Skill

• Designing a new database from scratch.
• Adding complex domains (e.g., "Add Social Features" or "Add Inventory Management").
• Deciding between SQL (Relational) vs NoSQL (Document/Graph).
• Troubleshooting architectural bottlenecks (Deadlocks, Hot partitions).
• Documenting data models with Entity-Relationship Diagrams (ERD).

Core Concepts

1. Relational Modeling (SQL)

Normalization (The Rules)

• 1NF: Atomic values. (No comma-separated lists).
• 2NF: No partial dependencies. (All non-keys depend on the whole primary key).
• 3NF: No transitive dependencies. (Non-keys depend ONLY on the primary key, not other non-keys).