Relational Database Design
Access + SQL queries
What this proves
- Problem: spreadsheet-based staffing and project tracking was causing inconsistency, limited analysis, and poor scalability.
- Method: designed normalized entities, bridge tables, metadata rules, and query patterns for projects, employees, clients, assets, tickets, and services.
- Outcome: replaced spreadsheet thinking with a structured model built for queryability, reporting consistency, and future operational growth.
Live proof surface
The public-safe proof for this project is the database methodology page and ERD PDF. The original classroom presentation is not currently published, so this page only exposes the artifact that is actually available now.