Friday, March 9, 2012

Reporting Service Performance

I have developed a Windows Forms Control that renders ReportingService reports as a metafile, This way the reports can be shown on as 'Crystal Reports' does in the wysiwyg way. But when the reports contain some hundered pages (and that happens often) the rendering of one page takes up to 3 seconds. The reason for this is not the SQL statement (it is a simple listing of 15000 records in one table). Is there a way to speed this up without using caches or snapshots? The Controls main feature must be that it can easily show and print reports.
The Control is based on the following code: http://blogs.msdn.com/bryanke/articles/71491.aspxThe image rendering extension was not really designed to be used this way
and is known to have issues with large reports. Bryan's code is a interim
approach until we have the supported set of report controls available in VS
Whidbey.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dasirr" <Dasirr@.discussions.microsoft.com> wrote in message
news:0BE027EA-51C5-4B4E-BC32-2CC51EE01E0C@.microsoft.com...
>I have developed a Windows Forms Control that renders ReportingService
>reports as a metafile, This way the reports can be shown on as 'Crystal
>Reports' does in the wysiwyg way. But when the reports contain some
>hundered pages (and that happens often) the rendering of one page takes up
>to 3 seconds. The reason for this is not the SQL statement (it is a simple
>listing of 15000 records in one table). Is there a way to speed this up
>without using caches or snapshots? The Controls main feature must be that
>it can easily show and print reports.
> The Control is based on the following code:
> http://blogs.msdn.com/bryanke/articles/71491.aspx

No comments:

Post a Comment