Execute DDL Task logging disappears after applying SQL Server 2008 SP2
I am using various SSIS packages to manage different Analysis Services (SSAS) databases. The packages create the necessary DDL for processing the dimensions and partitions in the SSAS databases and then run the DDL using Execute DDL tasks. I've been using SSIS logging to capture the log information for the Execute DDL Tasks and directing that log data to a SQL Server table. I've noticed that since the application of SP2 I only get the 'Started building processing schedule.' log message for the Execute DDL Tasks and none of the other event log entries. This has happened at a couple of the sites that I support. Install SP2 = no logging (with the one exception) from the Execute DDL Task steps. Is this a known issue? I did a couple of searches and didn't find anything. Thanks, Ray
October 19th, 2010 9:58pm

Hello Ray, Does the package complete successfully? If you are using a Script Task to do the custom logging then this could be the result. You must be able to see the Package End message, too. is this the case? Arthur My Blog
Free Windows Admin Tool Kit Click here and download it now
October 19th, 2010 10:17pm

Yes, the package completes successfully. One more "odd" thing: the log entries are there if I run the package from within Visual Studio...
October 19th, 2010 10:24pm

Please answer in full to the questions above, thank you.Arthur My Blog
Free Windows Admin Tool Kit Click here and download it now
October 19th, 2010 10:41pm

I'm using the 'SSIS log provider for SQL Server'. I have logging checked for every task in the package, and every event on every task. I get this at the end: End of package execution. The end result is that the cubes and dimensions are processed but the SSIS log data that I'm used to seeing for all of the events is not there. Is that what you're looking for?
October 19th, 2010 11:09pm

Was it SP2 for SQL Server 2008? How do you run the package?Arthur My Blog
Free Windows Admin Tool Kit Click here and download it now
October 19th, 2010 11:45pm

Yes, SQL Server 2008 SP2. We were running SP1, Cumulative Update 5 (CU5) prior to this. The package is executed from a SQL Server Agent job step (Type: SQL Server Integration Services Package). The Package source is 'File System'. The job is usually on a schedule to run nightly.
October 19th, 2010 11:52pm

I asked the above question to make sure this article is what you need to skim through: https://connect.microsoft.com/SQLServer/feedback/details/491508/logging-of-ssis-tasks-are-incomplete-when-run-by-sql-agent-job?wa=wsignin1.0 If that helps, please mark this thread as resolved.Arthur My Blog
Free Windows Admin Tool Kit Click here and download it now
October 20th, 2010 4:50pm

I actually ran across this post last night. I tried adding a couple of EventHandlers to the package per the workaround and, Voila! The log messages are back. Thanks Arthur for taking the time...
October 20th, 2010 5:17pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics