sprockit.Error

[ v1.3 ] [ v1.4 ] [ v1.5 ] [ Back to Sprockit home page ]

Records in this table describe errors encountered and reported by Sprockit during processing.

Records in the table that are older (in days) than Sprockit's LogRetentionPeriod property are automatically deleted.

Column name1) Column type Description Notes
EventId INT Unique identifier for the error. IDENTITY
EventDateTime DATETIME The data and time at which the error was logged.
RL1 ExecutionId INT Identifies the sprockit.Execution from which this error was thrown. Since Sprockit v1.5.
SourceDb NVARCHAR(128) The name of the database in which the errored process object is found. Consistent with [ExecutionId]; shown here for convenience. For SSIS packages, this is the name of the catalog folder.
SourceSchema NVARCHAR(128) The name of the database schema in which the errored process object is found. Consistent with [ExecutionId]; shown here for convenience. For SSIS packages, this is the name of the SSIS project.
SourceObject NVARCHAR(128) The schema-scoped name of the errored process object is found. Consistent with [ExecutionId]; shown here for convenience. For SSIS packages, this is the name of the SSIS package, including the .dtsx extension.
ErrorMessage NVARCHAR(4000) The reported error message.
ErrorNumber INT The SQL Server error number of the reported error. Failed SSIS package executions always have [ErrorNumber] = 50000 – this is because Sprockit reads package failures from SSISDB execution logs and raises them internally as generic SQL errors.
ErrorSeverity INT The reported error severity.
ErrorState INT The reported error state.
ErrorLine INT The reported line number of the error. This can be useful for locating errors precisely in stored procedures configured directly as processes, provided that they do not contain nested elements – line numbers reported in errors that bubble up through a stack of SP calls and/or dynamic SQL execution may be difficult to interpret.

Failed SSIS package executions always have the same line number. This is because Sprockit reads package failures from SSISDB execution logs and raises them internally, so the line number refers to the location in Sprockit code where the error is raised.

Relationships with integrity enforced by a foreign key constraint have identifiers prefixed with FK; others are prefixed RL.

Click here to view the data model diagram.

References to other tables

Attributes
(in this table)
Referenced table Referenced attributes
(in referenced table)
RL1 ExecutionId sprockit.Execution ExecutionId

References to this table from others

Relationship Attributes
(in referencing table)
Referenced attributes
(in this table)
(None).

Page generated from database metadata by DbScout.


1)
Columns with names in bold are non-nullable; columns with underlined names are participants in the table's primary key.