November 25, 2008 at 7:23 am
Is this so "out there" that no one really works with SSIS this way?
Beer's Law: Absolutum obsoletum
"if it works it's out-of-date"
May 14, 2010 at 4:24 am
Hi,
I've got exactly the same problem, except I can't get Dts.Log to work at all (even when I have ScriptTaskLogEntry option switched on in Logging for the script task).
Re. the FireInformation method...
Basically, I've tried setting logging options at the script level (to override those at the package level), and also just setting them at the script level. I've tried various combinations of events to capture (at both of the above levels) - and found that the FireInformation method logs the event regardless of whether the Information or ScriptTaskLogEntry options are switched on. I've tried not logging the Source Name column. I've tried various values in the parameters to the FireInformation method, including setting the subComponent parameter to the name of the script, the name of the package, an empty string, something else, etc.
In all cases, I get 2 lines logged for each call to this method - one with the script name being recorded as the Source Name, and the other with the package name being recorded as the Source Name.
Sorry I have no solution. It certainly looks like a bug!
May 2, 2011 at 11:13 am
See this Article about implementing custom ssis logging various ways. http://pragmaticworks.com/Products/Business-Intelligence/BIxPress/ssis-logging-auditing-monitoring.aspx
October 1, 2012 at 1:19 pm
SSIS Guy (5/2/2011)
See this Article about implementing custom ssis logging various ways. http://pragmaticworks.com/Products/Business-Intelligence/BIxPress/ssis-logging-auditing-monitoring.aspx
Thanks for linking to an ad for a commercial product! Big help!
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply