[ v1.3 ] [ v1.4 ] [ v1.5 ] [ Back to Sprockit home page ]
Records in this table represent types of SQL error that are recoverable (or “retryable”). A recoverable error is usally an intermittent fault that, if it occurs (causing process execution to fail), the only action you would take is to restart the failed process.
Normally, when a process handler catches an error thrown from a stored procedure, it updates the process's status to Errored and makes an entry in sprockit.Error. Conversely, if the message number of the SQL Server error appears in this table, no error is logged and the process's status is set to Ready, making it again available for selection by an available handler.
Care should be taken when designating error types as recoverable – errors that are likely to recur indefinitely will cause processing to enter an infinite loop. Transaction deadlocks (error number 1205) that cause the database engine arbitrarily to kill one process are a good example of recoverable errors and are configured in this table by default.
| Column name1) | Column type | Description | Notes | |
|---|---|---|---|---|
| PK | ErrorNumber | INT | The number of an error that, when encountered, should result in the failed process being retried. | |
| Notes | NVARCHAR(1024) | Narrative information about the recoverable error (for example, why it is considered recoverable). |
Relationships with integrity enforced by a foreign key constraint have identifiers prefixed with FK; others are prefixed RL.
| Attributes (in this table) | Referenced table | Referenced attributes (in referenced table) |
|
|---|---|---|---|
| (None). | |||
| Relationship | Attributes (in referencing table) | Referenced attributes (in this table) |
|---|---|---|
| (None). | ||
Page generated from database metadata by DbScout.