1
Vote

most recent failed execution failed

description

I built 8 ssis reporting pack connected on different 8 servers.
On 2 servers, the report "most recent failed execution" never end.
I applied the corrections of indexing [internal].[event_message_context], [internal].[executable_statistics], [internal].[operation_messages], [internal].[event_messages], [internal].[execution_component_phases] and modified the procedure [internal].[append_execution_component_phases] with SET TRANSACTION ISOLATION LEVEL SERIALIZABLE.

I have about 2 M rows in event_messages, operation_messages and event_message_context

comments

jamiet wrote Apr 9, 2013 at 2:36 PM

Hi,
That report does indeed suffer from performance issues and you will undoubtedly hit those issues with 2m rows in [catalog].[event_messages]. I wish that were not the case and I apologise that it is. I am in the process of making changes to sort it out but I don't expect those changes to be completed in the foreseeable future (life tends to get in the way I'm afraid).

Jamie