Back to work
Data Engineering·2025·Johnson Matthey
Claims Operations Warehouse
SQL Server warehouse and stored-procedure toolkit for claims operations, with referential integrity and cascading deletes.
SQL ServerT-SQLStored ProceduresETL
- Context
- Johnson Matthey's claims team worked from raw Excel extracts with no referential integrity, making claim history and profit/loss tracking error-prone.
- Timeline
- Delivered 2025
- Role
- Schema design, T-SQL, stored procedures
What I built
- A normalized SQL Server schema covering the full claims lifecycle.
- Four stored procedures: claim CRUD, detail CRUD, P/L tracking, and FK-safe cascading delete.
- A T-SQL load process moving raw Excel extracts into a clean operational store.
Architecture
Database
SQL ServerNormalized schema
Logic
T-SQLStored procedures
Load
Excel extractStaged import
Interesting decisions
Decision
FK-safe cascading delete
Deleting a claim without cleaning up its dependent records corrupts the P/L history. A dedicated cascading-delete procedure walks foreign keys in the right order, so one delete call can't leave orphaned rows.
Result
Claims operations moved off raw Excel extracts onto a normalized store with referential integrity, with stored procedures replacing manual edits.
More case studies
Full-stack
Jumbo / InterStar
Full e-commerce and ERP system. Storefront returning soon after a compliance update.
Read case study
Data Engineering
Lab Data Pipeline
Manual lab operations replaced with a self-updating cloud pipeline.
Read case study
AI & Automation
Competitive Intelligence Agent
An AI agent that runs weeks of market research in minutes.
Read case study