Ghost in the SQL Data Whiteboard System Explained: How the Investigator's Board Solves Cases

The Ghost in the SQL Data whiteboard system is the feature that transforms raw query results into a living investigation. Without it, you would just be running SELECT statements into the void — with it, every filtered table, chart, and hunch becomes a pinned piece of evidence you can physically connect. For a detective game built on databases, the Ghost in the SQL Data whiteboard system is what makes deduction feel tactile rather than abstract.

Released on October 29, 2026, by solo developer Isaac Menard, Ghost in the SQL Data asks you to solve Paris crimes by querying a year of emergency switchboard calls. The game currently sits at a "Positive" rating with 82% of 34 user reviews recommending it, and critics like ITmedia have called it "an unusual mystery game that developers will get hooked on." Here's how the board actually works and how to use it well.

What the Ghost in the SQL Data Whiteboard System Actually Does

The whiteboard — described in the game's store listing as an "investigator's board" — is a separate workspace layered on top of your SQL terminal. Once you run a query and get a result set you care about, you can pin that result, its associated chart, or a freeform note to the board. From there, you draw connections between pins to build a visual theory of the case.

Think of it as the bridge between two halves of the game:

The board doesn't solve anything for you. It's a thinking tool, not an answer key. That distinction matters — community reports suggest the later cases give you only the question and expect you to build the entire chain of reasoning yourself.

Why It Matters More Than It Sounds

Most detective games hand you a pre-built evidence wall. Ghost in the SQL Data makes you construct it. Because the underlying data is a real relational database (a year of Paris emergency calls), the board is the only place where your scattered findings become a coherent narrative. Skip it, and you'll be re-running the same queries from memory. Use it, and you'll spot the 14-minute gap between a fire report and the first witness that defines the opening case.

How to Use the Investigator's Board: A Step-by-Step Workflow

Here's a practical loop that works across every case, from the school fire tutorial to the Musée d'Orsay crown theft.

1. Read the case prompt carefully. Early cases teach SQL basics; later ones only give you the question.
2. Run a broad query first. Pull the full table or a wide date range before narrowing.
3. Filter and join. Use WHERE clauses and JOINs to isolate suspicious rows.
4. Pin anything interesting. A timestamp, a caller ID, an address — pin it immediately.
5. Chart the pattern. Turn call frequency or timing into a visual and pin the chart.
6. Write a note in your own words. Explain why the pin matters.
7. Connect the pins. Draw lines between related evidence to test your theory.
8. Re-query to confirm. If a connection feels weak, go back to SQL and verify.

That loop — query, pin, connect, verify — is the core rhythm of the Ghost in the SQL Data whiteboard system. Players who treat the board as an afterthought tend to hit walls in mid-game cases where multiple suspects share overlapping call patterns.

What to Pin (and What to Skip)

Not every result deserves board space. Over-pinning creates visual noise that makes connections harder to see.

A good rule of thumb: if you can't explain in one sentence why a pin is there, it probably shouldn't be.

Whiteboard vs. Terminal: How the Two Systems Divide the Work

New players sometimes wonder whether they should "live" in the SQL editor or the board. The answer is both, but for different reasons. The terminal is where truth lives — the data doesn't lie, and every claim you make on the board should trace back to a query you actually ran.

Community reports from early players suggest the most common mistake is trying to reason on the board without fresh query data — pinning a hunch you never verified. The board amplifies good data work; it can't substitute for it.

Tips for Getting More Out of the Ghost in the SQL Data Whiteboard System

A few habits separate smooth playthroughs from frustrating ones.

• Pin early, prune later. It's easier to remove a pin than to remember a result you forgot to save.
• Use charts aggressively. The game supports charting your results, and time-series charts of call volume are especially useful for spotting the "ghost" — the call that shouldn't exist.
• Name your notes like clues, not diary entries. "Caller 4471 called 14 min before fire report" beats "interesting."
• Revisit the board after every new query batch. Connections you missed become obvious once new pins land.
• Save anytime. The game supports saving at will, so there's no penalty for experimenting with board layouts.

The Ghost in the SQL Data whiteboard system rewards patience. Cases set in Paris — a nameless metro ticket, a stolen crown — often hinge on a single relationship between two pins that only becomes visible once you've charted enough data.

A Worked Example: The School Fire

The opening case is the clearest demonstration of the board's value. A call reported a school fire 14 minutes before the first witness saw flames. Your job: find who made that call using a year of Paris emergency switchboard data.

By the time you reach step 5, the board holds a visual chain from anomaly to suspect. That's the system working as intended.

How the Board Fits Into the Wider Game

Ghost in the SQL Data carries Steam Workshop support and a level editor, which means community-made cases will likely lean on the same board mechanics. The game also includes 38 Steam achievements, several of which appear tied to query milestones (one is literally called "Two Tables"). If you're chasing completion, the board is where you'll track which achievements you've triggered.

The game is playable on Steam Deck and supports ten languages, with AI used for programming assistance and translations per the developer's disclosure. At $9.99 (currently 10% off during the introductory offer), it's a compact, focused experience — and the whiteboard is a big part of why it doesn't feel like a dry SQL tutorial.

For the official store page, features list, and system requirements, see the Ghost in the SQL Data page on Steam.

FAQ

Is the Ghost in the SQL Data whiteboard system required to solve cases? Functionally, yes. Later cases give you only the question, and the board is where you assemble the evidence chain. You could theoretically track everything in your head, but the board exists to make complex multi-table cases manageable.

Can I pin charts as well as query results? Yes. The investigator's board lets you pin results, their charts, and your own notes, then connect clues between them. Charts are especially useful for spotting time-based anomalies in the Paris call data.

Does the board auto-solve deductions for me? No. The board is a visual workspace, not a solver. It stores and connects what you pin, but the reasoning — and the final accusation — is yours to make.

How does the whiteboard interact with the level editor and Workshop? The game includes a level editor and Steam Workshop support, so community cases may use similar board-based deduction. Check the Workshop for player-made investigations if you finish the main cases.