Variable Logging through SSISDB

• DamianC

  SSCrazy Eights

  Points: 8023

  More actions

  January 22, 2020 at 11:27 am

  #3717320

  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

• Phil Parkin

  SSC Guru

  Points: 246970

  More actions

  January 22, 2020 at 11:45 am

  #3717324

  Have a read here.

  You should be able to change your existing Script Task logging commands along those lines.

  I suggest that you try converting your existing 'success' messages to use FireInformation and see whether that gives you what you need.

  The absence of evidence is not evidence of absence.
  Martin Rees

  You can lead a horse to water, but a pencil must be lead.
  Stan Laurel

• DamianC

  SSCrazy Eights

  Points: 8023

  More actions

  January 22, 2020 at 2:18 pm

  #3717402

  Thanks Phil

   

  I'll take a look at that

  - Damian