Case Study

SQL Investigation Training

A technical training experience for support engineers that moved learners from foundational database reasoning into guided SQL practice, scenario-based investigation, and platform-aligned troubleshooting.

Overview

This curriculum supported Technical Support Engineers troubleshooting enterprise email security issues for administrator audiences in a SaaS environment. The program blended instructor-led instruction with guided SQL labs so learners could investigate issues, interpret outputs, and make evidence-based decisions during live case work.

Rather than teaching SQL as isolated syntax, the learning path intentionally moved from foundational database reasoning to applied investigation workflows that mirrored real support scenarios.

Challenge

Technical learners often memorize query examples without understanding how to adapt them under real troubleshooting conditions. That creates a gap between “knowing SQL” and using SQL effectively when investigating customer-facing issues.

The challenge was to design a training experience that built durable technical fluency, not just familiarity: helping engineers understand relational structure, reason through query changes, interpret results correctly, and transfer those skills into live product-context investigations.

Approach

I rebuilt the learning path into a scaffolded, practice-led progression:

foundational database reasoning
guided query practice
scenario-based investigation lab
platform-level transfer back into technical support workflows

Learners first built a mental model of relational databases and how tables connect. From there, they practiced SQL incrementally with structured examples, repeatedly returning to SQL City to apply each newly learned concept inside the murder mystery. That back-and-forth between instruction and application helped reinforce SQL as a reasoning tool rather than a memorized sequence of commands.

Solution

The final program included four major layers:

Outcome-focused objectives aligned to technical investigation tasks rather than isolated syntax exposure
Foundational database reasoning to explain structure, relationships, and query intent
Guided query practice with stepwise SQL examples and returned outputs to build fluency
Scenario lab + platform transfer so learners could investigate, refine, interpret, and then apply the same reasoning to support contexts

The core hands-on component was a scenario-based SQL investigation lab using the SQL Murder Mystery format. Learners formed hypotheses, refined queries iteratively, tested constraints, and interpreted results in a way that mirrored real troubleshooting workflows rather than rote completion.

My Role

I owned the training end-to-end, serving as both designer and facilitator.

rebuilt the program from a lecture-heavy format into a scaffolded, practice-led learning path
strengthened technical accuracy through self-upskilling and validation of SQL/database concepts for an engineer audience
designed the core scenario-based SQL investigation lab requiring hypothesis formation, query refinement, and result interpretation
produced a complete delivery kit including slides, instructor notes, and guided lab materials for repeatable delivery
facilitated group and independent practice with checkpoints focused on reasoning and output interpretation rather than rote syntax
aligned exercises to real support investigation behaviors and iterated based on learner feedback and observed performance trends

Outcome

This project demonstrates how I design technical learning for transfer, not just completion. The structure moved learners from conceptual understanding into iterative query refinement and finally into investigation behaviors that aligned to real enterprise support work.

It also shows how I build repeatable delivery systems: not just slides, but a full learning progression with labs, facilitation support, and practical checkpoints focused on evidence-based reasoning.

Selected Screens

Instruction screen for the SQL Murder Mystery scenario lab explaining the investigation setup and asking learners to retrieve the missing crime scene report using SQL — **Scenario Lab Introduction** — The SQL Murder Mystery lab shifted learning from passive explanation into investigative reasoning. Learners were introduced to a concrete problem and then asked to use SQL to uncover evidence step by step.

Learning objectives slide showing progression from relational database understanding to SQL investigation tasks and application in Proofpoint databases — **Outcome-Focused Objectives** — The objectives made the learning progression explicit: understand relational structure, use SQL deliberately, solve an investigation scenario, and apply that reasoning back to platform work.

Diagram of relational database structure and table relationships used to explain how data connects across entities in a database — **Foundational Database Reasoning** — Early instruction built the conceptual model first, helping learners understand relational structure, table relationships, and why query logic works the way it does.

SQL training slide showing a practical example of SELECT with WHERE and AND, using returned data to build fluency in conditional filtering and result interpretation — **Guided Query Practice** — Structured examples helped learners build fluency through incremental query refinement before sending them back into the scenario to apply the same ideas in context.

SQL Murder Mystery activity screen showing learners joining multiple tables and comparing results to identify patterns, witness clues, and suspects during the investigation — **Scenario-Based Multi-Table Investigation** — This is where the scenario became real problem-solving. Learners joined tables, compared outputs, and refined hypotheses, using SQL as an investigative reasoning tool rather than a memorized command list.

Applied SQL screen showing multi-table joins and aliased result columns, illustrating how learners transfer SQL skills back into realistic support investigation workflows — **Platform Transfer** — Later instruction connected the same SQL reasoning back to realistic support-style data work, reinforcing how query fluency supports accurate troubleshooting and case analysis.