Søren Eggert Lundsteen Olsen
8db226d2b6
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> |
||
|---|---|---|
| .. | ||
| SQLInsight.Agent | ||
| SQLInsight.Collectors | ||
| SQLInsight.Community | ||
| SQLInsight.Connectivity | ||
| SQLInsight.Contracts | ||
| SQLInsight.Core | ||
| SQLInsight.Hub | ||
| SQLInsight.Licensing | ||
| SQLInsight.Notifications | ||
| SQLInsight.Reports | ||
| SQLInsight.Repository | ||
| SQLInsight.Rules | ||
| SQLInsight.Servers | ||
| SQLInsight.Updates | ||
| SQLInsight.Web | ||