June 19, 2012 at 9:21 am
I was hoping to find an answer for this:
In sysssislog table, the executionID changes for the same package twice. For example, on the prevalidate phase, the executionID is 19EF7848-F626-4AF6-8B5F-0F419530597E. But this executionID changes to DA549ABD-27CC-4965-9DA0-FC701FB8F92C when the package starts executing.
To find more information on this, I read the BOL entry about the sysssislog table and it states that (as a special note on ExecutionID):
Running a single package might create log entries with different values for the ExecutionID element. For example, when you run a package in SQL Server Data Tools, the validation phase might create log entries with an ExecutionID element that corresponds to SQL Server Data Tools. However, the execution phase might create log entries with an ExecutionID element that corresponds to dtshost.exe. For another example, when you run a package that contains Execute Package tasks, each of these tasks runs a child package. These child packages might create log entries that have a different ExecutionID element than the log entries that the parent package creates.
I am at a loss to understand this behavior. Shouldn't the executionID remain same throughout the execution of the package? I am considering using the packageGUID as my identifier so that I can get around this issue, but any help on this would be appreciated. TIA.
June 19, 2012 at 10:38 am
Ok. I think I found the answer to this.
The execution ID changes when you run the package through BIDS. But if you run it from the dtexec command line, It does not change. Probably some other processes changing it on the fly in BIDS???
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply