how to link executionid of sysdtslog90

I have enabled logging using database.

When I try to query the sysdtslog90 table using System::ExecutionInstanceGUID to link executionid - it is not matching.

Any resolution?

Thanks

The variable System::ExecutionInstanceGUID always matches the sysdtslog90.executionid column when I try it.

Are the times matching up? Are you looking in the right table? Try using a Script Task to fire an event with the ExecutionInstanceGUID in the description text, so that it is logged and you can compare the two values in the same row.

|||

It worked when I pass the System::ExecutionInstanceGUID as VARCHAR parameter instead of GUID in SQL Task parameter mapping. And when the stored procedure recieves the same parameter as uniqueidentifier

sorry for my late response.

Thanks

how to link executionid of sysdtslog90

I have enabled logging using database.

When I try to query the sysdtslog90 table using System::ExecutionInstanceGUID to link executionid - it is not matching.

Any resolution?

Thanks

The variable System::ExecutionInstanceGUID always matches the sysdtslog90.executionid column when I try it.

Are the times matching up? Are you looking in the right table? Try using a Script Task to fire an event with the ExecutionInstanceGUID in the description text, so that it is logged and you can compare the two values in the same row.

|||

It worked when I pass the System::ExecutionInstanceGUID as VARCHAR parameter instead of GUID in SQL Task parameter mapping. And when the stored procedure recieves the same parameter as uniqueidentifier

sorry for my late response.

Thanks

|||

I just ran into the same issue. I noticed that all of a sudden the executionid's between sysdtslog90 and the logging table modeled from project real (audit.executionlog) were not matching. I changed the execute sql task that calls the audit.usp_OnBeginPackageEvent stored procedure to use the System::ExecutionInstanceGUID variable as a varchar instead of GUID and now all of sudden they match. Anyone have any idea why this is happening? I know it used to work, and on the service pack sp2.

|||I don't know why it's happening, but I've encountered the same thing a few times.

how to link executionid of sysdtslog90

I have enabled logging using database.

When I try to query the sysdtslog90 table using System::ExecutionInstanceGUID to link executionid - it is not matching.

Any resolution?

Thanks

The variable System::ExecutionInstanceGUID always matches the sysdtslog90.executionid column when I try it.

Are the times matching up? Are you looking in the right table? Try using a Script Task to fire an event with the ExecutionInstanceGUID in the description text, so that it is logged and you can compare the two values in the same row.

|||

It worked when I pass the System::ExecutionInstanceGUID as VARCHAR parameter instead of GUID in SQL Task parameter mapping. And when the stored procedure recieves the same parameter as uniqueidentifier

sorry for my late response.

Thanks

|||

I just ran into the same issue. I noticed that all of a sudden the executionid's between sysdtslog90 and the logging table modeled from project real (audit.executionlog) were not matching. I changed the execute sql task that calls the audit.usp_OnBeginPackageEvent stored procedure to use the System::ExecutionInstanceGUID variable as a varchar instead of GUID and now all of sudden they match. Anyone have any idea why this is happening? I know it used to work, and on the service pack sp2.

|||I don't know why it's happening, but I've encountered the same thing a few times.