Ghost in the SQL Data Level Editor: Build Your Own SQL Detective Cases

The Ghost in the SQL Data level editor is one of the most underrated features in Isaac Menard's indie detective sim, and it's the reason the game keeps giving long after you've closed your final case file. Released on Steam on October 29, 2026, this $9.99 puzzle game asks you to solve Paris-based mysteries using real SQL queries — and the built-in editor, paired with Steam Workshop integration, lets players design and share their own investigations. If you've finished the campaign and want more, or you're a developer curious about how the editor works before buying, this guide covers what the Ghost in the SQL Data level editor actually offers.

What the Level Editor Actually Does

According to the official Steam store page, Ghost in the SQL Data ships with a documented "Includes level editor" feature tag alongside Steam Workshop support. That combination is significant: it means custom cases aren't just local experiments — they can be published, downloaded, and played by the entire community.

The core game is built around a simple loop. You're given a question — say, who called the Paris Emergency Switchboard 14 minutes before a witness saw a school on fire — and you use SQL to filter, join, and interrogate a year's worth of call data. The editor extends that loop by letting you author the question, the underlying tables, and the solution path yourself.

Here's how the editor's role breaks down compared to the base game:

The editor isn't a separate app — it's integrated into the game client, so you're working with the same query interface you use to solve official cases.

Getting Started With the Ghost in the SQL Data Level Editor

Based on the feature set described on the official Ghost in the SQL Data Steam page, the editor is accessible from within the game itself. Because the game emphasizes learning SQL progressively — early cases teach the basics, later ones only hand you the question — the editor likely assumes some familiarity with SELECT statements, JOINs, and WHERE clauses.

A practical workflow for first-time creators looks like this:

1. Play through at least the tutorial cases. You need to understand how the game frames questions and what query complexity feels fair.
2. Sketch your mystery on paper first. Decide the culprit, the incriminating record, and the red herrings before touching the editor.
3. Build your data tables. Every case needs source data — calls, tickets, records — that contains both the answer and enough noise to make the search interesting.
4. Write the question. The best cases give players a single, clear objective, not a checklist.
5. Test your solution path. Run your own queries to confirm the case is solvable and that no shortcut bypasses the intended logic.
6. Publish to Steam Workshop. Once satisfied, upload and tag your case appropriately.

Player experience tip: Community reports suggest testing your custom case with someone who hasn't seen your solution. If they solve it in two queries, your data is too clean.

Designing Tables That Teach

The base game's data is deliberately messy — a year of Paris emergency calls means duplicates, nulls, and inconsistent formatting. Your custom tables should mirror that texture. A case where every column is perfectly labeled and every row is unique teaches nothing.

Consider these design patterns:

• Include at least one JOIN requirement. Two related tables force players to think relationally.
• Seed plausible false positives. A suspect who called the switchboard for an unrelated reason makes filtering meaningful.
• Use realistic date ranges. The game's Paris setting spans a full year, so time-based filtering is a natural skill to test.

Steam Workshop: How Custom Cases Reach Players

The presence of the Steam Workshop tag on the store page is the clearest signal that the Ghost in the SQL Data level editor is meant for community content, not just personal tinkering. Workshop integration typically means:

For creators, this is a low-friction distribution channel. You don't need to host files or build a website — the Workshop handles delivery, and Steam Cloud (also listed as a supported feature) keeps your own progress synced across machines.

What Makes a Workshop Case Worth Downloading

Community reports from similar editor-driven games suggest a few consistent winners:

• Clear premise in the title. "The Missing Métro Ticket" beats "Case 1."
• Honest difficulty labeling. Don't tag a JOIN-heavy case as beginner.
• A satisfying "aha" moment. The answer should feel earned, not stumbled upon.
• No dead ends. Every table you include should have a purpose.

How the Editor Fits the Game's Educational Mission

Ghost in the SQL Data is tagged as Education and Tutorial on Steam, and that framing matters for the editor. The campaign is explicitly structured to teach SQL — the store description notes that early cases teach the basics while later ones only give you the question. Player-made content extends that curriculum indefinitely.

Think of the editor as a teaching tool in two directions:

This is a rare case where the level editor isn't a novelty — it's structurally aligned with what the game is trying to do. A player who builds a case about a stolen crown from the Musée d'Orsay has to think like both a designer and a database architect.

Accessibility Considerations for Creators

The base game supports adjustable text size, subtitle options, custom volume controls, and is playable at your own pace with no quick-time events. When you design custom cases, keep those same principles in mind:

• Write clean, readable question text. Avoid dense paragraphs.
• Don't rely on color alone to distinguish table columns.
• Keep case length reasonable. A 30-minute custom case is a big ask for a download.

Common Pitfalls When Building Custom SQL Cases

Even with a solid editor, first-time creators tend to make the same mistakes. Community reports and general design principles point to a few recurring issues:

The Ghost in the SQL Data level editor rewards restraint. The best custom cases are small, tight, and built around a single clever query.

A Sample Case Structure

Here's a conceptual template you can adapt:

1. Premise: A witness reports a break-in at a Paris apartment.
2. Tables: calls (switchboard log), residents (building registry).
3. Question: "Which resident called the switchboard before the reported time but lives in a different arrondissement?"
4. Solution logic: JOIN on resident ID, filter by call timestamp, exclude matching arrondissements.
5. Red herrings: Two residents with unrelated calls in the same window.

That structure tests JOINs, filtering, and comparison operators without overwhelming the player.

Frequently Asked Questions

Is the Ghost in the SQL Data level editor free to use? Yes. The editor is included with the base game, which launched at $9.99 (with a 10% introductory discount through November 12, 2026). There's no separate editor purchase.

Can I share custom cases with other players? Yes. The game supports Steam Workshop, so published cases can be downloaded and played by the community. Steam Cloud also keeps your local progress synced.

Do I need to know SQL to use the level editor? You'll need a working grasp of SELECT statements, JOINs, and filtering. The campaign teaches these progressively, so finishing the tutorial cases first is strongly recommended before building your own.

Does the Ghost in the SQL Data level editor support other languages? The base game ships with 10 interface languages, but custom case text depends on what the creator writes. Community reports suggest English-first cases dominate the Workshop, so note your case's language clearly in its description.

Final Thoughts

The Ghost in the SQL Data level editor turns a focused $9.99 detective puzzle into an ongoing creative platform. With Steam Workshop distribution, a campaign that already teaches SQL fundamentals, and a design philosophy built around real database queries, it's a feature that deserves far more attention than its single store tag suggests. Whether you're building your first two-table case or publishing a full Paris mystery series, the editor gives you the tools — the rest is up to your query skills.