August 5, 2009 at 1:10 am
SJ,
SSIS is designed as a batch system that transforms some data input into some data output. So output is supposed to be put into some file or table that you can examine after running the package.
This imples that output in the meaning of "PRINT" makes no real sense in this context, because you would normally not see it at all, as your package will run in a background process on an arbitrary server.
If you want to see debugging output more than SSIS itself provides (as you see in the output window while debugging or in the sysdtslog90 table afterwards) you will have to programmatically add it. You can do this through SQL or script tasks adding rows to the sysdtslog90 table or by writing event handlers.
To increase the number of messages in the output window you can try the menu item "SSIS->Logging". This shows a dialog where you can enable or disable events being logged. You will have to turn on logging on package level (the root node) to get things logged and you should select a logging provider (use "SSIS log provider fro SQL server" to redirect the events to the sysdtslog90 table).
Playing around with the different events should give you the events you desire.
mfg
Guenter
Viewing post 1 (of 2 total)
You must be logged in to reply to this topic. Login to reply