Consider the following scenario:
- You install Service Pack 1 for Microsoft SQL Server 2008 R2.
- You run a SQL Server Integration Services (SSIS) package by using the dtexec utility (DTExec.exe) or the SQL Server Agent.
In this scenario, some logging events are missing in the output. For example, if you run the SSIS package that writes to a text file, various OnInformation, OnProgress, Diagnostic, OnPostExecute, and PackageEnd events may be missing from the text file. This behavior occurs even though the package finishes fully and successfully.Notes
- This issue also occurs in SQL Server 2008 after you install Service Pack 2 for Microsoft SQL Server 2008.
This issue does not occur if you run the SSIS package by using Execute Package Utility (dtexecui.exe) or the DtsDebugHost.exe process. The Execute Package Utility is a graphical UI for the dtexec command prompt tool. The DtsDebugHost.exe process debugs an SSIS package from the Business Intelligence Development Studio (BIDS) environment.
This issue occurs because of a regression from before Service Pack 1 for SQL Server 2008 R2 and before Service Pack 2 for SQL Server 2008.
This issue is already fixed in SQL Server 2008 R2 Service Pack 2 (SP2) and in SQL Server 2008 Service Pack 3 (SP3).
Cumulative update information
SQL Server 2008 R2 Service Pack 1
The fix for this issue was first released in Cumulative Update 8. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
Cumulative update package 8 for SQL Server 2008 R2 Service Pack 1
Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 Service Pack 1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To work around the issue, run the SSIS package by using the Execute Package Utility (dtexecui.exe) instead of the dtexec utility (dtexec.exe).
For more information about the dtexec Utility (dtexec.exe), go to the following MSDN website:
For more information about how to run a SSIS package, go to the following MSDN website: