ssisreportingpack Issue Tracker Rss Feed

Commented Issue: most recent failed execution failed [24155]

jamiet — Tue, 09 Apr 2013 13:36:45 GMT

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: ** Comment from web user: jamiet **

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

Created Issue: most recent failed execution failed [24155]

yann_nguyen — Tue, 09 Apr 2013 13:10:28 GMT

Created Issue: sp_ssiscatalog feature: show duration of leaf level executables [23721]

jamiet — Wed, 19 Dec 2012 12:48:54 GMT

Often you don't want to know how long containers, only the actual tasks themselves. Build something into sp_ssiscatalog that enables one to see this.

this should help:
select e.executable_name,duration_in_minutes=execution_duration/1000/60,duration_in_seconds=execution_duration/1000,execution_duration,execution_path
from ssisdb.catalog.executable_statistics es
inner join ssisdb.catalog.executables e on es.executable_id = e.executable_id
and es.execution_id = e.execution_id
and e.executable_name = reverse(left(reverse(execution_path), charindex('\', reverse(execution_path)) -1))
--order by execution_id desc
where es.execution_id = 10438
and execution_path like '\Root\ETLJobStageOrders~[8~]\PKG Thread 0\ThreadController\ETLJob Stages~[1~]\PKG Exec Stage\Main Actuals\SEQC Main Actuals\FELC Loop over TargetLoadDates~[7~9]%' escape '~'--
order by execution_duration desc

Commented Issue: Inconsistent Behavior in Links to reports using an Expression [21451]

jamiet — Thu, 16 Aug 2012 12:00:16 GMT

When I preview the reports in BIDS 2010, the links from dashboard.rdl to other reports works fine. When I deploy the project to a Denali CTP3/SP 2010 SP1 integrated report server instance, any text boxes that are using an expression to determine the report spcified in the text box action genereate an error that the rdl file can't be found.

The item 'http://denalictp3/SSISReportingPack/Execution' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item 'http://denalictp3/SSISReportingPack/Execution' cannot be found.

I can work around this by adding .rdl to the report name specified in the action expression (screenshot attached), redeploy and it works fine in SharePoint. However, I cannot use the links is VS 2010 preview any more unless I remove the .rdl extension

BTW, Overall I really like this!
Comments: ** Comment from web user: jamiet **

Hmmm, thanks Drewsky. Have you tried this on the RTM release and if so, does it still occur?

It sounds like something I would have noticed straightaway if it were happening to me. Don't worry, tho, I won't be closing the issue.

Closed Issue: Error TwelveMonthExecutionSummary.rsd is not found [22814]

jamiet — Thu, 16 Aug 2012 11:57:51 GMT

When previewing the SSRS project in SSDT, it came up with the following error:
"Could not find file 'C:\SSIS Reporting Pack\TwelveMonthExecutionSummary.rsd'"

This can be fixed by renaming the file name from "TwelveMonthExectionSummary.rsd" to "TwelveMonthExecutionSummary.rsd"

See attached screenshots.
Comments:

fixed.

Commented Issue: Error TwelveMonthExecutionSummary.rsd is not found [22814]

jamiet — Sun, 27 May 2012 09:02:40 GMT

OK, fixed and a new, modified, .msi is now available.

Commented Issue: Error TwelveMonthExecutionSummary.rsd is not found [22814]

jamiet — Sun, 27 May 2012 08:45:38 GMT

Damn, I thought I had fixed that. Thank you very much Julie.

Created Issue: Error TwelveMonthExecutionSummary.rsd is not found [22814]

mssqlgirl — Thu, 24 May 2012 06:02:47 GMT

Created Issue: Execution report too slow [22777]

jamiet — Wed, 16 May 2012 10:11:23 GMT

In an example a "select * from exec_stats_recursed" (where exec_stats_recursed is a CTE in the query that drives this report) took 8mins to return ~4000rows and was still going. It also brought my workstation to its knees (4 CPUs all at 100%).

For reference:
select * from exec_stats - 9252 rows in 4seconds
select * from generated_executables - 4533 rows in 5seconds
select * from anchor - 4535 rows in 5seconds
select * from exec_stats_recursed - ~4000rows in 8minutes at which point I killed it

Clearly this query can't handle big data volumes. This was an extreme case because a ForEach Loop had 4520 iterations but still - this is not good.

Created Issue: Bug: parent of a loop iteration is not correctly being calculated as the loop container [22491]

jamiet — Wed, 11 Apr 2012 14:02:57 GMT

In "execution executale duration.dtsx" we have the following query:
WITH [exec_stats] AS (
SELECT em.[execution_path],SUBSTRING(em.[execution_path],1,LEN(em.[execution_path]) - CHARINDEX('\',REVERSE(em.[execution_path]),1)) AS [parent_execution_path]
FROM ( SELECT distinct em.[operation_id],em.[execution_path] FROM [catalog].[event_messages] em WHERE em.[operation_id] = @ExecutionId
UNION
SELECT es.[execution_id],es.[execution_path] FROM [catalog].[executable_statistics] es WHERE es.[execution_id] = @ExecutionId
) em
)
select * from exec_stats
Problem is that this creates the problem seen in attached "exec_stats_results.PNG" - the parent of \Root\ETLJobStageOrders[2] is incorrectly returned as \Root. The data that causes this a warning message in event_messages that is attributed to the loop iteration (e.g. "ETLJobStageOrders:Warning: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.")
That error message is returned by:
select message,execution_path
from catalog.event_messages
where operation_id = @ExecutionId and execution_path = '\Root\ETLJobStageOrders[2]'
In short, we are incorrectly calculating the parent of a loop iteration when that loop iteration appears in catalog.event_messages.execution_path. This creates the situation that you can see in attached report screenshot "erroneous_execution_duration_report.png" where a loop iteration incorrectly appears as the child of the root.

Created Issue: Inconsistent Behavior in Links to reports using an Expression [21451]

DrewskyJones — Tue, 06 Sep 2011 18:59:07 GMT

Created Issue: "Dataflow" and "Dataflow outputs" should contain package & dataflow name in breadcrumbs [21359]

jamiet — Wed, 17 Aug 2011 21:30:11 GMT

"Dataflow" and "Dataflow outputs" should contain package & dataflow name in breadcrumbs. Currently only goes down to folder name.

Created Issue: Clickthrough from "folder" report to "executions" report resulted in error [21358]

jamiet — Wed, 17 Aug 2011 21:20:09 GMT

An attempt was made to set a report parameter 'Status' that is not defined in this report. (rsUnknownReportParameter)
Specifically, I clicked on the link in the "executions" column

Created Issue: "Last 5 executions" on dashboard- tooltip should show logging level [21357]

jamiet — Wed, 17 Aug 2011 20:52:47 GMT

"Last 5 executions" on dashboard- tooltip should show logging level. Thus easy to show difference verbose logging can make.

Created Issue: "Last 5 executions" on dashboard should show currently executing executions [21356]

jamiet — Wed, 17 Aug 2011 20:52:01 GMT

"Last 5 executions" on dashboard should show currently executing executions. It doesn't currently.

Created Issue: Provide dataflow and/or component throughput. [21238]

jamiet — Wed, 27 Jul 2011 08:34:29 GMT

This maybe should reflect active time & wall clock time.

Closed Issue: Change doc links to bit.ly links [19723]

jamiet — Sun, 16 Jan 2011 23:22:06 GMT

Comments: Resolved with changeset 57224.

Created Issue: Change doc links to bit.ly links [19723]

jamiet — Sun, 16 Jan 2011 23:18:09 GMT

Closed Issue: Provide a link to the documentation from the reports [19722]

jamiet — Sun, 16 Jan 2011 22:50:13 GMT

Comments: Resolved with changeset 57222.

Created Issue: Provide a link to the documentation from the reports [19722]

jamiet — Sun, 16 Jan 2011 22:41:25 GMT