Hi,I have created a package and enabled logging on sql2008. when run in BIDS, it creates the sysssislog table in the specified database and logs all events I have checked in the logging options.after this I uploaded it into the ssis repository and created a job in the sql server agent. when i run the same package through this job, the log lines are incomplete. the are missing lines forsome tasks.I enabled logging by checking just the first checkbox, so that all child elements in the package should inherit the logging settings. I think the sql server agent does not work correctly with the inherited log settings.Can someone reproduce this issue?here are the steps how to do this in just 5 minutes:- create a new ssis package- create one or better two simple tasks (SQL Task, statement "select 1")- go in the menu to "SSIS"-"logging"- check the first checkbox in the treeview- add a new log provider for sql server and choose a database- go in the details tab and click onPreExecute and onPostExecute- run the package=> a system table will be created in the chosen database with name "sysssislog"=> check the contents, it should be at least 4 lines for the package and 2 lines for each task- open SSMS- connect to ssis and upload the package- connect to sql server and add a job for the uploaded task- run the job- check the syssslog-table=> the result should be incomplete nowI have reproduced this on 2 machines, both running on win2003srv and sql2008.It would help me a lot if anyone could confirm this issue.thank you!

Hi, Please check the following thread http://social.msdn.microsoft.com/forums/en-US/sqlintegrationservices/thread/02874b24-0e09-4b71-bf45-2db26d1310bc/ He configured the logging for each task. thanks-Let us TRY this | Dont forget to mark the post(s) that answered your question

Thank you for your fast response.But unfortunately this is no option for me.I have about 40-50 packages, for whichI want to enable logging to get information about task duration.My intention is to create statistics about ETL processes, to identify weak points and how a growth of data has impact on runtimes.And of course also I like to get more information about errors.I like to set up logging by choosing a logprovider and the log events once for each package.I started to enable logging for one package by clicking all tasks (about 30 items), but this took so much time.Using saved events does not save time, as you still have to do almost the same number of mouse clicks.Is there no other option?

Hi,I have created a package and enabled logging on sql2008. when run in BIDS, it creates the sysssislog table in the specified database and logs all events I have checked in the logging options.after this I uploaded it into the ssis repository and created a job in the sql server agent. when i run the same package through this job, the log lines are incomplete. the are missing lines forsome tasks.I enabled logging by checking just the first checkbox, so that all child elements in the package should inherit the logging settings. I think the sql server agent does not work correctly with the inherited log settings.Can someone reproduce this issue?here are the steps how to do this in just 5 minutes:- create a new ssis package- create one or better two simple tasks (SQL Task, statement "select 1")- go in the menu to "SSIS"-"logging"- check the first checkbox in the treeview- add a new log provider for sql server and choose a database- go in the details tab and click onPreExecute and onPostExecute- run the package=> a system table will be created in the chosen database with name "sysssislog"=> check the contents, it should be at least 4 lines for the package and 2 lines for each task- open SSMS- connect to ssis and upload the package- connect to sql server and add a job for the uploaded task- run the job- check the syssslog-table=> the result should be incomplete nowI have reproduced this on 2 machines, both running on win2003srv and sql2008.It would help me a lot if anyone could confirm this issue.thank you! Hi Jay,I have been working on SQL 2005 and never faced this issue.I follow the same steps that you have mentioned.You could raise an issue with SQL team if you feel this is some sort of bug.Hope this helps !! Sudeep| My Blog

This does seem like a bug to me. Although the guy in the quoted thread found a workaround, its my understanding that everything should be logged.Maybe someone from MS or an MVP is watching this thread and could clarify?every day is a school day

Hi Jay,I have been working on SQL 2005 and never faced this issue.I follow the same steps that you have mentioned.You could raise an issue with SQL team if you feel this is some sort of bug. Hope this helps !! Sudeep| My Blog Thank you for testing.Can yousearchthe XML of your package for<DTS:Property DTS:Name="LoggingMode">0</DTS:Property>It seems like thispropertyis set in SSIS 2008 forevery item(tasks, loops,...) and unless I do check the checkbox explicitly, it is set to zero for all items and I can't notice any property that sets the inheritance of logging.

I am not using SSIS 2008.In 2005 I see the same value but dont see the issue u are facing.It seems like some bug you could raise it with MS.Hope this helps !! Sudeep| My Blog

Thank you Sudeep.I have already created a Feedback at MS quite some time ago, but got no answer so far.https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=491508Can somebody please confirm this issue with a SQL 2008 instance?If yes, please raise the counter in the link above, so that MScan start to take care of this issue.

Jay, I was able to duplicate this on SQL Server 2008 SP1. I've escalated it to the SSIS team.John Welch | www.mariner-usa.com | www.agilebi.com | ssisUnit.codeplex.com

Thank you, John.How much time do you think will the SSIS team need to give feedback?Can I see the progress of your call/ticket somewhere?Iwant to keep to up with that topic.

They will respond to this thread if there is anything they can add.John Welch | www.mariner-usa.com | www.agilebi.com | ssisUnit.codeplex.com

If you are talking about some missing logs related to OnPreExecute and OnPostExecute, this is a bug in SQL 2008 and will be fixed in next major release.Please workwith PSS if you need to get a hotfix

In the short term, Jay, you can work around this by adding OnPreExecute and OnPostExecute event handlers to your main package. In the event handler, you can use an Execute SQL Task to log the Pre- and PostExecute events to the log. All the values you should need are stored in System variables scoped to the event handler.Cho Yeung, does next major release mean SP2 for 2008, or SQL Server 2008 R2?John Welch | www.mariner-usa.com | www.agilebi.com | ssisUnit.codeplex.com

Next major release is actually SQL11

Thank you for this information.I don't wanted to use custom logging because of the additional work for every single ssis project.Enable logging of Pre- and Post-Execute for all my projects was my idea - I alreadybuilt a report view that can extract runtimes of tasks from the logs, evenwhen loops were used. (btw. something like an Instance ID or similarwould be great in the log result to find related log lines.)Well, so I will change my logging plans ... or search another way to easily enable logging (Pre-/PostExecute/Error) for my packages.I am thinink of a Script/AddIn that does change the XML source to set the logging property explicitly to '1' before uploading the package into theSQL DB store.

I have found a workaround, at least it worked for me, details in my blog. . . . http://www.drowningintechnicaldebt.com/ShawnWeisfeld/archive/2010/02/03/upgrade-from-ssis-2005-to-2008-broke-ssis-logging.aspxhttp://www.shawnweisfeld.com

Shawn's workaround seems to be the best!the 'bugfix' is to create an empty event handler for each event (onPreExecute/onPostExecute/...) at package level.visit his blog for details...Thanks Shawn!

FYI A hotfix for this got posted 2 days agoFIX: Log entries are missing for the OnPreExecute event and the OnPostExecute event in SQL Server 2008 Integration Serviceshttp://sqlblog.com/blogs/jamie_thomson/ | @jamiet | About me

I had similar problems with PipelineRowSentEvents I think this is SSIS 2008 bug ... only happens in sql 2008 Job... didnt happen in 2005 and R2. I was trying to capture PipeLine Events and as soon as I schedule package in SQL Agent Job some events are missings in the log table. Pre and Post Execute events are fine... I dont have issue with that. Returns 25 Records SELECT * FROM [BIxPress_JIRA_BIX1151].[dbo].[SSISDataFlowExecutionLog] where executionid='{9B41EF37-E298-4C0A-B4FB-77A33191D40A}' --Works (in BIDS) Returns 11 Records SELECT * FROM [BIxPress_JIRA_BIX1151].[dbo].[SSISDataFlowExecutionLog] where executionid='{24465DAE-8049-4089-8A5A-1AF452AC6904}' --Doesnt Works (in JOB) --Select * From [BIxPress_JIRA_BIX1151].[dbo].SSISPackageExecutionLog I found that for some reason package executed from JOB doesn’t generate full history of dataflow execution. SSIS-Tutorials-FAQs | Convert DTS to SSIS | Document SSIS | SSIS Tasks | Real-time SSIS Monitoring

I know this is old - but I've got an issue where a production server has been upgraded (from 2005 to 2008r2) and now my SSIS tasks seem to have some logging issues. The tasks themselves seem to log (to a text file, not the database) but there is not longer the date/time stamp on each entry like their used to be. Is this a different manifestation of the same bug or is there some option that previously date stamped by default and now doesn't?