SSIS Reporting Pack

New Post: Cannot open SSISReportingPack.rptproj

gnanau — Fri, 14 Jun 2013 18:32:03 GMT

I downloaded SSIS Reporting Pack.msi from this site and ran it. Files were create in folder E:\SSIS Reporting Pack. When I double click on SSISReportingPack.rptproj I get message saying "Unknown error" and that's it!

I have SQL Server Data Tools installed with SQL Server 2012, as well as Visaul Studion 2010 on my machine.

Any idea what might be the problem?

Source code checked in, #72254

jamiet — Tue, 04 Jun 2013 20:29:53 GMT

should not be in source control

Source code checked in, #72253

jamiet — Tue, 04 Jun 2013 20:16:10 GMT

unknown checkout

Source code checked in, #72252

jamiet — Tue, 04 Jun 2013 20:13:53 GMT

never checkin .user files

Source code checked in, #72129

jamiet — Fri, 17 May 2013 08:38:47 GMT

reorganised folder structure

Updated Release: v0.4 (May 21, 2012)

jamiet — Mon, 29 Apr 2013 08:02:59 GMT

There are a few bug fixes in this release however the main change is that the Execution report no longer displays loop iterations as executables.

The installer (that you download from this site) will place the report .rdl files into a folder on your hard drive, by default this location is "C:\SSIS Reporting Pack" (you have the option to change this when you run the installer).

Installation Steps

As well as the report files it also creates a file called SSISReportingPack.rptproj - this is a Reporting Services project that, when double-clicked, will open up in Visual Studio (assuming that you have the SQL Server 2012 development tools installed on your machine). From there you will be able to deploy the reports in that report project just as you would any other report project.

Released: v0.4 (May 21, 2012)

Mon, 29 Apr 2013 08:02:59 GMT

Installation Steps

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

Source code checked in, #71659

jamiet — Tue, 26 Mar 2013 08:38:42 GMT

@operation_type renamed to @action

Created Release: DB v1.0.3.0 (Mar 15, 2013)

jamiet — Fri, 15 Mar 2013 21:55:55 GMT

2 new features:

new parameter @ot provided as a short form of @operation_type
relative-duration visualisation

Released: DB v1.0.3.0 (Mar 15, 2013)

Fri, 15 Mar 2013 21:55:54 GMT

2 new features:

new parameter @ot provided as a short form of @operation_type
relative-duration visualisation

Source code checked in, #71536

jamiet — Fri, 15 Mar 2013 21:50:43 GMT

relative_duration, @ot

Source code checked in, #71452

jamiet — Mon, 11 Mar 2013 23:02:45 GMT

change erroneous date in pre-deployment comment

Created Release: DB v1.0.2.0 (Mar 11, 2013)

jamiet — Mon, 11 Mar 2013 22:23:44 GMT

A number of under-the-hood changes from previous version. Main benefits for the user is that (by default) documentation will appear in the messages tab when sp_ssicatalog is executed.

Released: DB v1.0.2.0 (Mar 11, 2013)

Mon, 11 Mar 2013 22:23:44 GMT

A number of under-the-hood changes from previous version. Main benefits for the user is that (by default) documentation will appear in the messages tab when sp_ssicatalog is executed.

Source code checked in, #70701

jamiet — Wed, 02 Jan 2013 09:45:44 GMT

duration_in_seconds will now return a value for currently executing executions. Previously it returned NULL.

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

Source code checked in, #70585

jamiet — Wed, 12 Dec 2012 23:49:30 GMT

print alteration

Source code checked in, #70584

jamiet — Wed, 12 Dec 2012 23:40:04 GMT

moved objects from schema sp_ssis_catalog to sp_ssiscatalog