Use this tab to save information regarding a Data Transformation Services (DTS) package execution. You can specify where you want to save the errors for a package, and decide whether the package should stop when an error is encountered. You can also have the package execution status saved to Microsoft® SQL Server™ and specify to stop the package when problems are encountered with the log file.
Log package execution to SQL Server
Specify that you want to save the package and step execution data into the msdb database. Information about the package will be saved in the sysdtspackagelog file, while information about each step in the package will be saved in the sysdtssteplog. Steps that are not executed have no information stored for them in the log.
Specify the name of the server whose msdb database will be the storage area for the logging information.
Use Windows Authentication
Specify to use Windows Authentication for login to the instance of SQL Server where the msdb database resides.
Use SQL Server Authentication
Specify to use SQL Server Authentication for login to the SQL Server database where the msdb database resides.
Specify a user name for the msdb database connection.
Specify a password for the msdb database connection.
Fail package on log error
Specify that a failure to write the log to the server will stop the package from executing further. Log errors can be caused by having the event log buffer sized too small, or renaming the server log table.
Specify that you want immediately to delete all logs of this package from the msdb database saved .
Specify the name of the file where package and step status and error information will be written. This file will contain a list of the steps not executed, in addition to the steps that were executed and their result. The file can be on a local drive or on a mapped drive. If the file does not exist at package run time, the file will be created. The file does not have a default extension assigned to it; you must put the extension on the file name. The most common extension is .txt.
Display the Select File dialog box, where you can search the local computer or mapped drives for an existing error file. If an existing error file is used, the status and error information for the package will be appended.
Fail package on first error
Specify that a first step failure stops the entire package. Any remaining steps or tasks are not run. If this option is not selected, then the package will continue to run regardless of any failures in any of the steps. The package will complete with a successful status.
Write completion status to event log
Specify that you want to write the package execution status to the Microsoft Windows® application log. This option is only available on computers running Windows NT 4.0 and Windows 2000. For more information, see How to view the Windows application log (Windows).