16.8.11 error-resolution-map

Preserve the complete error and execution context instead of guessing an error number or cause.

Diagnosis Order

1. Collect the full ERR-XXXXX message, SQL/command, and occurrence time.
2. Record server and SDK versions, edition, target database/owner/table, and connection options.
3. Check the message in the Error Code Dictionary.
4. Apply symptom-specific procedures from Troubleshooting.
5. Verify recovery with the same input and validation queries after corrective action.

Do not assign an arbitrary error code from part of a message or recommend a destructive workaround without reproducing the problem.