Task marker
Looks like `QBM-K-*`, `QER-K-*`, `TSB-K-*`, etc.
Open primary explorer Recipe: Start from a concrete DBQueue task marker
Start with the clue you have, then jump to the right source-derived explorer. This page routes static evidence; it is not live queue telemetry.
Looks like `QBM-K-*`, `QER-K-*`, `TSB-K-*`, etc.
Open primary explorer Recipe: Start from a concrete DBQueue task marker
Looks like `QBM_PDBQueueInsert_Bulk`, `_Single`, `_WaitForComp`, or case variants.
Open primary explorer Recipe: Start from QBM_PDBQueueInsert* routine evidence
Looks like `dbo.QER_TUBaseTree`, `dbo.QBM_ZPrePropTable`, trigger/procedure names, or module URLs.
Open primary explorer Recipe: Start from a SQL module
Contains backslash-separated config paths such as `QER\ITShop\…` or `Common\ProcessState`.
Open primary explorer Recipe: Start from a config reference
Looks like `INSERT into`, `UPDATE not`, `DELETE PersonWantsOrg`, or another write clue.
Open primary explorer Recipe: Start from a DML target pattern
Looks like table/read markers such as `inserted`, `deleted`, `QBMDBQueueCurrent`, `PersonWantsOrg`, or `BaseTree`.
Open primary explorer Recipe: Start from a read reference
Starts with `@`, e.g. `@GenProcID`, `@DBQueueElements_01`, `@SlotNumber`, `@XUser`.
Open primary explorer Recipe: Start from a SQL parameter name
Looks like a task namespace prefix such as `QBM`, `QER`, `TSB`, `ADS`, `LDP`, `ATT`, `RMS`, `CPL`, or `RPS`.
Open primary explorer Recipe: Compare route behavior by task family
Use when the clue is mixed-routine, multi-family, high task fan-out, route fan-out, or config-heavy behavior.
Open primary explorer Recipe: Triage high-signal DBQueue hotspots
Use when you need to know whether missing task/config/DML/read/parameter evidence is a corpus gap before concluding behavior.
Open primary explorer Recipe: Audit evidence gaps before concluding behavior
Use when the clue is only “DBQueue”, “ChangeLimit”, or an unfamiliar token.
Open primary explorer Recipe: Start a DBQueue investigation broadly