Transfer Error Messages Task
The Transfer Error Messages task transfers one or more SQL Server user-defined error messages between instances of SQL Server. User-defined messages are messages with an identifier that is equal to or greater than 50000. Messages with an identifier less than 50000 are system error messages, and cannot be transferred by using the Transfer Error Messages task.
The Transfer Error Messages task can be configured to transfer all error messages, or only the specified error messages. User-defined error messages may be available in a number of different languages and the task can be configured to transfer only messages in selected languages. A us_english version of the message that uses code page 1033 must exist on the destination server before you can transfer other language versions of the message to that server.
The sysmessages table in the master database contains all the error messages—both system and user-defined—that SQL Server uses.
The user-defined messages to be transferred may already exist on the destination. An error message is defined as a duplicate error message if the identifier and the language are the same. The Transfer Error Messages task can be configured to handle existing error messages in the following ways:
- Overwrite existing error messages.
- Fail the task when duplicate messages exist.
- Skip duplicate error messages.
At run time, the Transfer Error Messages task connects to the source and destination servers by using one or two SMO connection managers. The SMO connection manager is configured separately from the Transfer Error Messages task, and then is referenced in the Transfer Error Messages task. The SMO connection manager specifies the server and the authentication mode to use when accessing the server. For more information, see SMO Connection Manager.
Transferring Between Instances of SQL Server
The Transfer Error Messages task supports a source and destination that is SQL Server 2000 or SQL Server 2005. There are no restrictions on which version to use as a source or destination.
Events
The task raises an information event that reports the number of error messages that have been transferred.
The Transfer Error Messages task does not report incremental progress of the error message transfer; it reports only 0% and 100 % completion.
Execution Value
The execution value, defined in the ExecutionValue property of the task, returns the number of error messages that have been transferred. By assigning a user-defined variable to the ExecValueVariable property of the Transfer Error Message task, information about the error message transfer can be made available to other objects in the package. For more information, see Integration Services Variables and Using Variables in Packages.
Log Entries
The Transfer Error Messages task includes the following custom log entries:
- TransferErrorMessagesTaskStartTransferringObjects This log entry reports that the transfer has started. The log entry includes the start time.
- TransferErrorMessagesTaskFinishedTransferringObjects This log entry reports that the transfer has finished. The log entry includes the end time.
In addition, a log entry for the OnInformation event reports the number of error messages that were transferred, and a log entry for the OnWarning event is written for each error message on the destination that is overwritten.
Security and Permissions
To create new error messages, the user that runs the package must be a member of the sysadmin or serveradmin server role on the destination server.
Configuring the Transfer Error Messages Task
You can set properties through SSIS Designer or programmatically.
For more information about the properties that you can set in SSIS Designer, click one of the following topics:
- Transfer Error Messages Task Editor (General Page)
- Transfer Error Messages Task Editor (Messages Page)
- Expressions Page
For more information about how to set these properties in SSIS Designer, click the following topic:
Configuring the Transfer Error Messages Task Programmatically
For more information about programmatically setting these properties, click the following topic:
See Also
Concepts
Integration Services Tasks
Creating Package Control Flow