Hi
I want to do custom logging (not ssis logging from ssis > logging menu) but I obviously don't want the logging to participate in the main transaction otherwise i'll lose the log records.
DTC is set up. I've a parent (controller) package. The package TransactionOption property is required and the rest (except for logging 'execute sql' tasks) are set to 'not supported'. So it's a basic all or nothing affair except for the logging inserts.
When I try to insert into the logging table it hangs on that task. Ive used profiler and im getting insert locks with blocking session id -2.
It seems as though the transaction start (required) is locking the schema, but allows reads). I've gone through all the properties of the connection manager and execute sql task and nothing is shouting at me. The connections RetainSameConnection property is false so I assumed the connections would be pooled and thus can cope with a 'not supported' task. It doesn't. So I tried to create a new connection and assigned the sql task to this (as not supported) but this doesn't help either, still hangs.
It must be pretty common to log errors independently of a transaction within that package - in the same way as you can do it in a try / catch via sql. But none the wiser through ssis. Any ideas?
Thanks, Jon