Updated: June 10, 2016
Stores error detail for log shipping jobs. This table is stored in the msdb database.
The tables related to history and monitoring are also used at the primary server and the secondary servers.
|Column name||Data type||Description|
|agent_id||uniqueidentifier||The primary ID for backup or the secondary ID for copy or restore.|
|agent_type||tinyint||The type of log shipping job.|
0 = Backup.
1 = Copy.
2 = Restore.
|session_id||int||The session ID for the backup/copy/restore/ job.|
|database_name||sysname||The name of the database associated with this error record. Primary database for backup, secondary database for restore, or empty for copy.|
|sequence_number||int||An incremental number indicating the correct order of information for errors that span multiple records.|
|log_time||datetime||The date and time at which the record was created.|
|log_time_utc||datetime||The date and time at which the record was created, expressed in Coordinated Universal Time.|
|source||nvarchar||The source of the error message or event.|
|help_url||nvarchar||The URL, if available, where more information about the error can be found.|
This table contains error detail for the log shipping agents. Each error is logged as a sequence of exceptions. There can be multiple errors (sequences) for each agent session.
In addition to being stored on the remote monitor server, the information related to the primary server is stored on the primary server in its log_shipping_monitor_error_detail table, and information related to a secondary server is also stored on the secondary server in its log_shipping_monitor_error_detail table.
To identify an agent session, use columns agent_id, agent_type, and session_id. Sort by log_time to see the errors in the order in which they were logged.
About Log Shipping (SQL Server)
System Tables (Transact-SQL)