Database Detective: Minor Crimes Division

A crime procedural written in queries

Database Detective: Minor Crimes Division puts players behind the desk of a rookie investigator in the fictional city of Los Zorangeles, tasked with clearing a backlog of unsolved cases for the Minor Crimes Division — everything from littering to, eventually, considerably less minor offenses. The twist, and the entire premise, is that every case is solved by writing actual SQL queries: filtering suspect tables, joining witness statements against alibi records, and narrowing down a perpetrator from a pool of evidence the same way a real analyst would interrogate a database. New players are eased in with a short in-fiction manual — reviewers describe it as under 20 pages and genuinely well-written — plus a helpful in-game assistant character and clear, specific error messages when a query goes wrong, so no prior SQL experience is assumed or required.

What comes through most strongly across the review sample, though, isn't the mechanic itself so much as the writing wrapped around it. Reviewers describe an elaborate, deadpan sense of humor that consistently subverts expectations — cases that sound ominous in their setup routinely resolve into something absurdly mundane, and the game's own fictional internet, its "copOS" interface, and its recurring cast of Los Zorangeles characters are treated as a real, internally consistent world rather than a thin skin over a query trainer. Notably, a large share of the most detailed reviews come from people who use SQL professionally — data engineers, DBAs, backend developers — several of whom frame the game as funnier and more engaging than they expected specifically because it gets the texture of real data work right, jokes about clean datasets and cooperative stakeholders included.

One anecdote from the review sample captures that comic sensibility well: a reviewer describes showing the game's "War Criminal" case to a partner who works as a data engineering lead, inviting her to guess the nature of the crime before the evidence was revealed. Her guesses ran toward the genuinely horrific, in keeping with a case labelled a war crime, only for the reveal to land on something completely mundane and absurd instead. That rug-pull structure — a serious setup followed by a deliberately anticlimactic punchline — recurs often enough in reviewer anecdotes that it reads as a defining part of the game's comic voice rather than a one-off gag. Some reviewers also note that Thomas Hsu previously released a much shorter free comedy game, and describe discovering Database Detective as a direct result of enjoying that earlier release, a small but telling sign of a developer building a recognizable comic voice across more than one project.

Where the difficulty curve breaks

The English-language review corpus sits at 547 reviews with a "review score" of 9, translating to Steam's Overwhelmingly Positive tier, with 533 positive against just 14 negative. That ratio holds up under closer reading: even reviewers who raise serious complaints about the later cases almost always still recommend the game, and the sample includes very few reviews that read as outright regretful purchases.

Where the criticism concentrates is squarely on pacing. Several reviewers describe the first several cases as effectively a tutorial — approachable, well-scaffolded, and forgiving — before a sharp jump in both SQL complexity and pure deductive reasoning kicks in around the midpoint. One reviewer specifically frames the shift as a change in what the game is actually testing: early cases reward correctly written queries, but later ones increasingly demand guessing what specific piece of evidence the developer intended players to notice next, sometimes requiring manual cross-referencing across a sprawling in-game internet with over 200 fictional profiles. A separate, recurring complaint is that failing a query submission in these later cases forces a full restart of that case section, discarding partial progress — a design choice more than one reviewer calls unnecessarily punishing given how much setup the late-game cases require. A few reviewers also flag rougher edges in the desktop-style window management the game uses to juggle multiple data tables at once, including a window-switch shortcut that only alternates between the two most recently used windows instead of cycling through everything open, and a close-window shortcut that can misfire text into an unrelated textbox.

What the achievement data shows

Steam's global achievement percentages for the game's 34 achievements back up the reviewer accounts of a front-loaded, then punishing, difficulty curve almost exactly. Early milestones like LEVEL_1 sit at 74.6% and LEVEL_2 at 73.4%, meaning roughly three-quarters of players who engage with achievements clear the opening stretch without much attrition. That completion rate falls steadily through the middle cases — LEVEL_4 sits at 49.4%, LEVEL_6 drops to 27.9%, and LEVEL_7 falls further to 13.9% — before cratering at the top end: LEVEL_9 sits at just 3.8%, LEVEL_10 and the FINISH achievement for completing the game both land at 2.9%, and a specific late-story achievement tied to confronting the city's ruling figure, ARREST_ZORAN, sits at 2.7%. That trajectory is a close match for what reviewers describe qualitatively — a game that starts nearly everyone off comfortably and then loses the large majority of its audience precisely in the stretch reviewers identify as the difficulty spike, rather than attrition being spread evenly across all ten cases.

Final verdict

Database Detective: Minor Crimes Division earns its overwhelmingly positive reception honestly: it's a genuinely funny, well-constructed piece of world-building that happens to use real SQL as its core mechanic, accessible enough for total beginners and engaging enough that working database professionals keep showing up in its review sample to vouch for it. The achievement data confirms what a meaningful slice of reviewers already say in plain terms — the back half of its ten cases asks for a level of patience and lateral deduction the front half doesn't prepare players for, and thin tooling around failed attempts and window management makes that climb harder than it should be. None of that erases what the game gets right in its writing and premise, but anyone going in expecting a uniformly gentle SQL tutorial from start to finish should adjust their expectations for the second half.