sqlinsight-pro/docs/dynamics-ax
Søren Eggert Lundsteen Olsen 8db226d2b6 Dynamics AX 3.0: batch STATUS checked against customer data
Cascorp's BATCH table: every STATUS 4 row has an end time and no exception
code (finished), STATUS 1 rows have no end time and starts long passed
(waiting). So AX 3.0 uses the same order as AX 4.0+: 0 Tilbageholdt,
1 Venter, 2 Udfører, 3 Fejl, 4 Afsluttet. The old assumption (0 Venter ...
4 Tilbageholdt) treated finished jobs as held and waiting ones as running.

SQLI-AX-003 skips waiting jobs planned more than BatchAbandonedDays (30)
ago: the customer has 25 such rows from 2007-2018 that no batch server
serves; they are dead rows, not a live alarm.

Adds docs/dynamics-ax/verificer-ax30-batchstatus.sql (read-only) to repeat
the check at other AX 3.0 customers.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-03 09:36:56 +02:00
..
schema-ax30.tsv Dynamics AX 3.0 reference schema (from a customer's AX 3.0 database) 2026-10-02 10:00:33 +02:00
schema-ax2009.documented.tsv Dynamics AX core: central detector, per-version schema adapters, read-access GRANT 2026-10-02 13:52:58 +02:00
schema-ax2012.documented.tsv Dynamics AX core: central detector, per-version schema adapters, read-access GRANT 2026-10-02 13:52:58 +02:00
verificer-ax30-batchstatus.sql Dynamics AX 3.0: batch STATUS checked against customer data 2026-10-03 09:36:56 +02:00