Define Entities and Relationships
ERDs establish which records belong together and how keys connect them. This gives the team a shared model before writing loading and query logic.
DATA ENGINEERING
Database Normalization
Organize raw sales data into a consistent SQL Server schema.
The Problem
Raw sales records need consistent entities, relationships, and keys before they can support reliable queries. When the same information is repeated across records, updates can become inconsistent; loading data without clear constraints can introduce invalid relationships. I led a team to address these data-modeling and loading problems in SQL Server.
The Approach
I led a six-person team working on entity relationship diagrams, schema design, automated loading, sequence-based keys, and stored procedures. We organized sales data for querying and used database constraints to enforce relationships and business rules.
Make Loading Repeatable
Automated load scripts turn data preparation into a process that can be rerun, rather than a sequence of manual database edits. Sequence-based keys provide identifiers for inserted records.
Enforce Rules in SQL Server
Integrity constraints and stored procedures put relationship checks and business logic in the database, where they can be applied consistently across data operations.
Project Deliverables
We delivered schema diagrams, repeatable load scripts, keys, constraints, and stored procedures to structure, load, and validate sales records in SQL Server.