Custom events information from a child package is not logged under the log provider context of the parent package in SQL Server 2005 Integration Services (910512)
The information in this article applies to:
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
SYMPTOMSIn Microsoft SQL Server 2005 Integration Services (SSIS),
you can use an Execute Package task to execute a child package from a parent
SSIS package. When you use an SSIS log provider to log event information from
the child package, the event information will be logged two times.
However, when you log custom events information
from a child package, you may notice that the event information is not logged
under the log provider context of the parent package. The information is logged only one time under the execution context of the child package. Therefore, it
may be difficult to understand which execution context of the parent package
relates to a particular set of entries that are logged by the child
package.MORE INFORMATIONAn SSIS package contains an Execute Package
task to execute a child package. The child package logs information from the
custom ExecuteSQLExecutingQuery event to an SSIS log provider for SQL Server. To determine the executionid field information of the parent package and of the child
package, use the following Transact-SQL statement: SELECT event,source,sourceid,executionid,starttime
FROM sysdtslog90 WHERE event in ('packagestart', 'packageend')
ORDER BY starttime desc,executionid
Query resultevent source sourceid executionid starttime
===================================================================================================================================
PackageEnd Parent C95DF672-ABB7-48E3-B7E7-E10B2E169854 0F09283C-798B-4FF2-AE0A-12BDE457FE31 11/11/2005 11:37:14
PackageStart Child2 D01AE7CE-A478-4B49-B8E2-536A498D419F C115AC89-F432-4860-B85F-EC55CFA69E08 11/11/2005 11:36:22
PackageEnd Child2 D01AE7CE-A478-4B49-B8E2-536A498D419F C115AC89-F432-4860-B85F-EC55CFA69E08 11/11/2005 11:36:22
PackageStart Parent C95DF672-ABB7-48E3-B7E7-E10B2E169854 0F09283C-798B-4FF2-AE0A-12BDE457FE31 11/11/2005 11:36:21
PackageEnd Parent C95DF672-ABB7-48E3-B7E7-E10B2E169854 324D48AC-2D2B-4A38-BAA2-7A79A86AD2E9 11/11/2005 11:32:05
PackageStart Child2 D01AE7CE-A478-4B49-B8E2-536A498D419F 67F0022D-0EFC-4925-A847-527DE29DBB14 11/11/2005 11:28:56
PackageEnd Child2 D01AE7CE-A478-4B49-B8E2-536A498D419F 67F0022D-0EFC-4925-A847-527DE29DBB14 11/11/2005 11:28:56
PackageStart Parent C95DF672-ABB7-48E3-B7E7-E10B2E169854 324D48AC-2D2B-4A38-BAA2-7A79A86AD2E9 11/11/2005 11:28:55
PackageEnd Parent C95DF672-ABB7-48E3-B7E7-E10B2E169854 6F97336F-4C25-4D6B-AD70-E0224E8D66CF 11/11/2005 11:27:05
PackageStart Parent C95DF672-ABB7-48E3-B7E7-E10B2E169854 6F97336F-4C25-4D6B-AD70-E0224E8D66CF 11/11/2005 11:26:27
PackageEnd Parent C95DF672-ABB7-48E3-B7E7-E10B2E169854 F8769CA4-3D7A-4FA2-9377-EA7C2978562A 11/11/2005 11:25:09
PackageStart Parent C95DF672-ABB7-48E3-B7E7-E10B2E169854 F8769CA4-3D7A-4FA2-9377-EA7C2978562A 11/11/2005 11:24:09
PackageEnd Parent C95DF672-ABB7-48E3-B7E7-E10B2E169854 40C5C8D2-BFF9-43EE-96D1-652A37BDBC27 11/11/2005 11:23:43
PackageStart Parent C95DF672-ABB7-48E3-B7E7-E10B2E169854 40C5C8D2-BFF9-43EE-96D1-652A37BDBC27 11/11/2005 11:23:42 The first four records show the executionid information of the
parent package and the child package. In this example, the executionid field
information of the parent package is 0F09283C-798B-4FF2-AE0A-12BDE457FE31 and
the executionid field information of the child package is
C115AC89-F432-4860-B85F-EC55CFA69E08. When you use the following
Transact-SQL statement to query log data of the Execute SQL task from the
database, assume that the sourceid field information of the task is
9471BA59-605F-4D32-8865-F6288CAB0256. You may notice that the information about
the ExecuteSQLExecutingQuery event only appears in the execution context of the child package: SELECT event,source,sourceid,executionid,starttime FROM sysdtslog90
WHERE sourceid='9471BA59-605F-4D32-8865-F6288CAB0256'
AND executionid in ('0F09283C-798B-4FF2-AE0A-12BDE457FE31','C115AC89-F432-4860-B85F-EC55CFA69E08')
Query resultevent source sourceid executionid starttime
===================================================================================================================================================================================
User:OnPreValidate Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 0F09283C-798B-4FF2-AE0A-12BDE457FE31 11/11/2005 11:36:22
OnPreValidate Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 C115AC89-F432-4860-B85F-EC55CFA69E08 11/11/2005 11:36:22
User:OnPostValidate Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 0F09283C-798B-4FF2-AE0A-12BDE457FE31 11/11/2005 11:36:22
OnPostValidate Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 C115AC89-F432-4860-B85F-EC55CFA69E08 11/11/2005 11:36:22
User:OnPreValidate Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 0F09283C-798B-4FF2-AE0A-12BDE457FE31 11/11/2005 11:36:22
OnPreValidate Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 C115AC89-F432-4860-B85F-EC55CFA69E08 11/11/2005 11:36:22
User:OnPostValidate Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 0F09283C-798B-4FF2-AE0A-12BDE457FE31 11/11/2005 11:36:22
OnPostValidate Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 C115AC89-F432-4860-B85F-EC55CFA69E08 11/11/2005 11:36:22
User:OnPreExecute Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 0F09283C-798B-4FF2-AE0A-12BDE457FE31 11/11/2005 11:36:22
OnPreExecute Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 C115AC89-F432-4860-B85F-EC55CFA69E08 11/11/2005 11:36:22
User:OnPreValidate Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 0F09283C-798B-4FF2-AE0A-12BDE457FE31 11/11/2005 11:36:22
OnPreValidate Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 C115AC89-F432-4860-B85F-EC55CFA69E08 11/11/2005 11:36:22
User:OnPostValidate Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 0F09283C-798B-4FF2-AE0A-12BDE457FE31 11/11/2005 11:36:22
OnPostValidate Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 C115AC89-F432-4860-B85F-EC55CFA69E08 11/11/2005 11:36:22
User:ExecuteSQLExecutingQuery Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 C115AC89-F432-4860-B85F-EC55CFA69E08 11/11/2005 11:36:22
User:ExecuteSQLExecutingQuery Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 C115AC89-F432-4860-B85F-EC55CFA69E08 11/11/2005 11:36:23
User:ExecuteSQLExecutingQuery Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 C115AC89-F432-4860-B85F-EC55CFA69E08 11/11/2005 11:36:23
User:OnPostExecute Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 0F09283C-798B-4FF2-AE0A-12BDE457FE31 11/11/2005 11:36:22
OnPostExecute Execute SQL Task (in child_2) 9471BA59-605F-4D32-8865-F6288CAB0256 C115AC89-F432-4860-B85F-EC55CFA69E08 11/11/2005 11:36:22 STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.REFERENCES For more information about how to
interpret data that is logged by using a SQL Server 2005 Integration Services
log provider, click the following article number to view the article in the
Microsoft Knowledge Base: 906563
How to interpret data that is logged by using a SQL Server 2005 Integration Services log provider
Modification Type: | Major | Last Reviewed: | 1/6/2006 |
---|
Keywords: | kbExpertiseAdvanced kbsql2005ssis kbprb KB910512 kbAudDeveloper kbAudITPRO |
---|
|