January 22, 2020 at 11:27 am
Hello
I have some packages that were created in 2008
I'm upgrading these to 2016
The 2008 packages log to sysssislog in a specific DB
There are a small number of script tasks that log variable values by creating a row in sysssislog with a message
The script task has been created using c# and posts the event message using Dts.Log
So, for example, it might log who an e-mail has gone to along with say a file location referenced in the mail, all made up using variables from the package
Ideally, I want to do away with this (if that's the recommended path) and use SSISDB logging instead
Basic works fine when logging pre, post and errors
I can also drill into the error context to see values after a failure
What I cannot see is values after a success
For example, an individual says they haven't recieved an e-mail and I want to check it should have gone to them OR a file should have been written to a specific location and it's missing
Is this possible or do I have to either write to an audit table, revert to sysssislog package logging or maybe even a mix of SSISBD and sysssislog
Thanks
- Damian
January 22, 2020 at 2:18 pm
Thanks Phil
I'll take a look at that
- Damian
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply