Biml and SSIS Frameworks - SQL Server Integration Services Design Patterns - page 572

,ev.EventDescription
From log.SSISEvents ev
Join log.SSISAppInstance ai
On ai.AppInstanceID = ev.AppInstanceID
Join cfg.Applications a
On a.ApplicationID = ai.ApplicationID
Join log.SSISPkgInstance cp
On cp.PkgInstanceID = ev.PkgInstanceID
And cp.AppInstanceID = ev.AppInstanceID
Join cfg.AppPackages ap
On ap.AppPackageID = cp.AppPackageID
Join cfg.Packages p
On p.PackageID = ap.PackageID
Where ev.AppInstanceID = Coalesce(@AppInstanceID,
ev.AppInstanceID)
And ev.PkgInstanceID = Coalesce(@PkgInstanceID,
ev.PkgInstanceID)
Order By EventDateTime Desc
go
print 'Rpt.ReturnEvents stored procedure created.'
print ''
Add a new report named Events , use the rpt.ReturnEvents stored procedure,
and remember to configure the dataset and report parameters. Add the alternating row
shading I demonstrated in the Errors report. The same expression will work in the
Events report:
=Iif(RowNumber(Nothing) Mod 2 = 0,"White","WhiteSmoke")
Return to the Application Instance report and add another column to the data table.
Label it Events and set the data grid value to Events as well. Open the Text Box Prop-
erties window for the Events data field and navigate to the Font page. Change the Col-
or property to Blue and the Effects property to Underline. On the Actions page, change
the Enable as an Action property to “Go to Report and the Specify a Report drop-down
to Events. Add a parameter mapping and map the AppInstanceID parameter n ame
to the [AppinstanceID] parameter value. Click the OK button to close the Text
Box Properties Editor. Let's test it!
The Application Instance report now appears, as shown in Figure A-30 .