reports running in VB.Net much slower than Visual Studio

I've been building reporting services reports for the last 6 months,
and we just got our reporting services server last week. I've started
deploying my reports to the reporting server, and I'm disappointed in
the speed of the reports in a VB.Net windows application. I'm running
the reports in remote processing mode (not local).
The reports generate much slower than they do in Visual Studio. The
reports generate REALLY slow, if the reports are viewed in print
layout mode. I'd like to be able to use the print layout view, so the
report will display the footers, page breaks, and page numbering
correctly.
The reports run great in Visual Studio. Does anyone have any
suggestions to make the reports in a VB.Net windows application run
like they do in Visual Studio? Can anyone explain why the performance
is so different between the two? Why does rendering the report in
print layout mode so much slower in VB vs. Visual Studio? Or should
it be the same?
I'm using reporting services 2005. Our reporting services server is
running on a separate server than our SQL database.The rendering engine is the same in VS 2005 development environment as that
on the server (this was not true in 2000 which is why sometimes you would
see some small differences). However, VS 2005 caches data. That can account
for some of the issues. Another issue is network transmission time. But, the
main time difference is when you preview in VS you are previewing html which
is many times faster than PDF or other types of formats.
RS shines at providing data quickly to the user. By deciding you want to
present a book (or an electronic paper report) you are not taking advantage
of the strengths of RS. The best way to design reports is to present 10-20
pages to the user (or less). Make extensive use of drill through (links that
pull up additional detail reports).
They are re-writing the rendering engine for 2008 and expect PDF (and other
formats) that are slow today to be quite a bit faster.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<billyburditt@.gmail.com> wrote in message
news:1185484622.910356.290840@.b79g2000hse.googlegroups.com...
> I've been building reporting services reports for the last 6 months,
> and we just got our reporting services server last week. I've started
> deploying my reports to the reporting server, and I'm disappointed in
> the speed of the reports in a VB.Net windows application. I'm running
> the reports in remote processing mode (not local).
> The reports generate much slower than they do in Visual Studio. The
> reports generate REALLY slow, if the reports are viewed in print
> layout mode. I'd like to be able to use the print layout view, so the
> report will display the footers, page breaks, and page numbering
> correctly.
> The reports run great in Visual Studio. Does anyone have any
> suggestions to make the reports in a VB.Net windows application run
> like they do in Visual Studio? Can anyone explain why the performance
> is so different between the two? Why does rendering the report in
> print layout mode so much slower in VB vs. Visual Studio? Or should
> it be the same?
> I'm using reporting services 2005. Our reporting services server is
> running on a separate server than our SQL database.
>|||On Jul 26, 4:42 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
wrote:
> The rendering engine is the same in VS 2005 development environment as that
> on the server (this was not true in 2000 which is why sometimes you would
> see some small differences). However, VS 2005 caches data. That can account
> for some of the issues. Another issue is network transmission time. But, the
> main time difference is when you preview in VS you are previewing html which
> is many times faster than PDF or other types of formats.
> RS shines at providing data quickly to the user. By deciding you want to
> present a book (or an electronic paper report) you are not taking advantage
> of the strengths of RS. The best way to design reports is to present 10-20
> pages to the user (or less). Make extensive use of drill through (links that
> pull up additional detail reports).
> They are re-writing the rendering engine for 2008 and expect PDF (and other
> formats) that are slow today to be quite a bit faster.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> <billyburd...@.gmail.com> wrote in message
> news:1185484622.910356.290840@.b79g2000hse.googlegroups.com...
>
> > I've been building reporting services reports for the last 6 months,
> > and we just got our reporting services server last week. I've started
> > deploying my reports to the reporting server, and I'm disappointed in
> > the speed of the reports in a VB.Net windows application. I'm running
> > the reports in remote processing mode (not local).
> > The reports generate much slower than they do in Visual Studio. The
> > reports generate REALLY slow, if the reports are viewed in print
> > layout mode. I'd like to be able to use the print layout view, so the
> > report will display the footers, page breaks, and page numbering
> > correctly.
> > The reports run great in Visual Studio. Does anyone have any
> > suggestions to make the reports in a VB.Net windows application run
> > like they do in Visual Studio? Can anyone explain why the performance
> > is so different between the two? Why does rendering the report in
> > print layout mode so much slower in VB vs. Visual Studio? Or should
> > it be the same?
> > I'm using reporting services 2005. Our reporting services server is
> > running on a separate server than our SQL database.- Hide quoted text -
> - Show quoted text -
Thanks for your response. For the last 6 months I've been converting
excel reports to reporting services. Some of the reports are over 50
pages. I've been really pleased with creating these reports in
reporting services. The reports look much better than the original
Excel reports, and from start to finish it only take a few minutes to
generate a pdf, which we send to our clients.
Putting the reports online or in a windows application with user
interactivity would have been icing on the cake. I can change some of
my reports to have a drill down, but several of the reports need to
show all the detail together. It's too bad reporting services only
supports an HTML version for the web. HTML doesn't display the
footers, page breaks, and page numbering like the pdf files. It also
does a post back when paging through the report, which is really slow
for a report like mine.
Interactive reports would have been awesome for my reports, but
they're just too big. You said 2008 engine will be much faster. This
will be great for a windows application. Do you know if 2008 will
have a different format than HTML for the web? I haven't found much
information on reporting services for 2008.|||You can render however you want (html, pdf, excel). If you do PDF that will
show in the browser. In particular PDF will be much much faster (I've been
promised, I haven't seen). So your reports can be displayed in your VB app
with PDF and you will/should see substantial performance improvements with
2008.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<billyburditt@.gmail.com> wrote in message
news:1185982595.638219.275480@.19g2000hsx.googlegroups.com...
> On Jul 26, 4:42 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
> wrote:
>> The rendering engine is the same in VS 2005 development environment as
>> that
>> on the server (this was not true in 2000 which is why sometimes you would
>> see some small differences). However, VS 2005 caches data. That can
>> account
>> for some of the issues. Another issue is network transmission time. But,
>> the
>> main time difference is when you preview in VS you are previewing html
>> which
>> is many times faster than PDF or other types of formats.
>> RS shines at providing data quickly to the user. By deciding you want to
>> present a book (or an electronic paper report) you are not taking
>> advantage
>> of the strengths of RS. The best way to design reports is to present
>> 10-20
>> pages to the user (or less). Make extensive use of drill through (links
>> that
>> pull up additional detail reports).
>> They are re-writing the rendering engine for 2008 and expect PDF (and
>> other
>> formats) that are slow today to be quite a bit faster.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> <billyburd...@.gmail.com> wrote in message
>> news:1185484622.910356.290840@.b79g2000hse.googlegroups.com...
>>
>> > I've been building reporting services reports for the last 6 months,
>> > and we just got our reporting services server last week. I've started
>> > deploying my reports to the reporting server, and I'm disappointed in
>> > the speed of the reports in a VB.Net windows application. I'm running
>> > the reports in remote processing mode (not local).
>> > The reports generate much slower than they do in Visual Studio. The
>> > reports generate REALLY slow, if the reports are viewed in print
>> > layout mode. I'd like to be able to use the print layout view, so the
>> > report will display the footers, page breaks, and page numbering
>> > correctly.
>> > The reports run great in Visual Studio. Does anyone have any
>> > suggestions to make the reports in a VB.Net windows application run
>> > like they do in Visual Studio? Can anyone explain why the performance
>> > is so different between the two? Why does rendering the report in
>> > print layout mode so much slower in VB vs. Visual Studio? Or should
>> > it be the same?
>> > I'm using reporting services 2005. Our reporting services server is
>> > running on a separate server than our SQL database.- Hide quoted text -
>> - Show quoted text -
> Thanks for your response. For the last 6 months I've been converting
> excel reports to reporting services. Some of the reports are over 50
> pages. I've been really pleased with creating these reports in
> reporting services. The reports look much better than the original
> Excel reports, and from start to finish it only take a few minutes to
> generate a pdf, which we send to our clients.
> Putting the reports online or in a windows application with user
> interactivity would have been icing on the cake. I can change some of
> my reports to have a drill down, but several of the reports need to
> show all the detail together. It's too bad reporting services only
> supports an HTML version for the web. HTML doesn't display the
> footers, page breaks, and page numbering like the pdf files. It also
> does a post back when paging through the report, which is really slow
> for a report like mine.
> Interactive reports would have been awesome for my reports, but
> they're just too big. You said 2008 engine will be much faster. This
> will be great for a windows application. Do you know if 2008 will
> have a different format than HTML for the web? I haven't found much
> information on reporting services for 2008.
>|||On Aug 1, 11:26 am, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
wrote:
> You can render however you want (html, pdf, excel). If you do PDF that will
> show in the browser. In particular PDF will be much much faster (I've been
> promised, I haven't seen). So your reports can be displayed in your VB app
> with PDF and you will/should see substantial performance improvements with
> 2008.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> <billyburd...@.gmail.com> wrote in message
> news:1185982595.638219.275480@.19g2000hsx.googlegroups.com...
>
> > On Jul 26, 4:42 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
> > wrote:
> >> The rendering engine is the same in VS 2005 development environment as
> >> that
> >> on the server (this was not true in 2000 which is why sometimes you would
> >> see some small differences). However, VS 2005 caches data. That can
> >> account
> >> for some of the issues. Another issue is network transmission time. But,
> >> the
> >> main time difference is when you preview in VS you are previewing html
> >> which
> >> is many times faster than PDF or other types of formats.
> >> RS shines at providing data quickly to the user. By deciding you want to
> >> present a book (or an electronic paper report) you are not taking
> >> advantage
> >> of the strengths of RS. The best way to design reports is to present
> >> 10-20
> >> pages to the user (or less). Make extensive use of drill through (links
> >> that
> >> pull up additional detail reports).
> >> They are re-writing the rendering engine for 2008 and expect PDF (and
> >> other
> >> formats) that are slow today to be quite a bit faster.
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >> <billyburd...@.gmail.com> wrote in message
> >>news:1185484622.910356.290840@.b79g2000hse.googlegroups.com...
> >> > I've been building reporting services reports for the last 6 months,
> >> > and we just got our reporting services server last week. I've started
> >> > deploying my reports to the reporting server, and I'm disappointed in
> >> > the speed of the reports in a VB.Net windows application. I'm running
> >> > the reports in remote processing mode (not local).
> >> > The reports generate much slower than they do in Visual Studio. The
> >> > reports generate REALLY slow, if the reports are viewed in print
> >> > layout mode. I'd like to be able to use the print layout view, so the
> >> > report will display the footers, page breaks, and page numbering
> >> > correctly.
> >> > The reports run great in Visual Studio. Does anyone have any
> >> > suggestions to make the reports in a VB.Net windows application run
> >> > like they do in Visual Studio? Can anyone explain why the performance
> >> > is so different between the two? Why does rendering the report in
> >> > print layout mode so much slower in VB vs. Visual Studio? Or should
> >> > it be the same?
> >> > I'm using reporting services 2005. Our reporting services server is
> >> > running on a separate server than our SQL database.- Hide quoted text -
> >> - Show quoted text -
> > Thanks for your response. For the last 6 months I've been converting
> > excel reports to reporting services. Some of the reports are over 50
> > pages. I've been really pleased with creating these reports in
> > reporting services. The reports look much better than the original
> > Excel reports, and from start to finish it only take a few minutes to
> > generate a pdf, which we send to our clients.
> > Putting the reports online or in a windows application with user
> > interactivity would have been icing on the cake. I can change some of
> > my reports to have a drill down, but several of the reports need to
> > show all the detail together. It's too bad reporting services only
> > supports an HTML version for the web. HTML doesn't display the
> > footers, page breaks, and page numbering like the pdf files. It also
> > does a post back when paging through the report, which is really slow
> > for a report like mine.
> > Interactive reports would have been awesome for my reports, but
> > they're just too big. You said 2008 engine will be much faster. This
> > will be great for a windows application. Do you know if 2008 will
> > have a different format than HTML for the web? I haven't found much
> > information on reporting services for 2008.- Hide quoted text -
> - Show quoted text -
I know you can export in those different formats, but can you display
the reports in a different format other than HTML on the web? HTML
doesn't display correctly and you have to post back to the server to
move through the pages of the document.
Billy|||Sure. When you request the rendering you can specify the format. Plenty of
people go right to PDF (HTML is much faster currently).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<billyburditt@.gmail.com> wrote in message
news:1186175875.359497.281210@.g4g2000hsf.googlegroups.com...
> On Aug 1, 11:26 am, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
> wrote:
>> You can render however you want (html, pdf, excel). If you do PDF that
>> will
>> show in the browser. In particular PDF will be much much faster (I've
>> been
>> promised, I haven't seen). So your reports can be displayed in your VB
>> app
>> with PDF and you will/should see substantial performance improvements
>> with
>> 2008.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> <billyburd...@.gmail.com> wrote in message
>> news:1185982595.638219.275480@.19g2000hsx.googlegroups.com...
>>
>> > On Jul 26, 4:42 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
>> > wrote:
>> >> The rendering engine is the same in VS 2005 development environment as
>> >> that
>> >> on the server (this was not true in 2000 which is why sometimes you
>> >> would
>> >> see some small differences). However, VS 2005 caches data. That can
>> >> account
>> >> for some of the issues. Another issue is network transmission time.
>> >> But,
>> >> the
>> >> main time difference is when you preview in VS you are previewing html
>> >> which
>> >> is many times faster than PDF or other types of formats.
>> >> RS shines at providing data quickly to the user. By deciding you want
>> >> to
>> >> present a book (or an electronic paper report) you are not taking
>> >> advantage
>> >> of the strengths of RS. The best way to design reports is to present
>> >> 10-20
>> >> pages to the user (or less). Make extensive use of drill through
>> >> (links
>> >> that
>> >> pull up additional detail reports).
>> >> They are re-writing the rendering engine for 2008 and expect PDF (and
>> >> other
>> >> formats) that are slow today to be quite a bit faster.
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >> <billyburd...@.gmail.com> wrote in message
>> >>news:1185484622.910356.290840@.b79g2000hse.googlegroups.com...
>> >> > I've been building reporting services reports for the last 6 months,
>> >> > and we just got our reporting services server last week. I've
>> >> > started
>> >> > deploying my reports to the reporting server, and I'm disappointed
>> >> > in
>> >> > the speed of the reports in a VB.Net windows application. I'm
>> >> > running
>> >> > the reports in remote processing mode (not local).
>> >> > The reports generate much slower than they do in Visual Studio. The
>> >> > reports generate REALLY slow, if the reports are viewed in print
>> >> > layout mode. I'd like to be able to use the print layout view, so
>> >> > the
>> >> > report will display the footers, page breaks, and page numbering
>> >> > correctly.
>> >> > The reports run great in Visual Studio. Does anyone have any
>> >> > suggestions to make the reports in a VB.Net windows application run
>> >> > like they do in Visual Studio? Can anyone explain why the
>> >> > performance
>> >> > is so different between the two? Why does rendering the report in
>> >> > print layout mode so much slower in VB vs. Visual Studio? Or should
>> >> > it be the same?
>> >> > I'm using reporting services 2005. Our reporting services server is
>> >> > running on a separate server than our SQL database.- Hide quoted
>> >> > text -
>> >> - Show quoted text -
>> > Thanks for your response. For the last 6 months I've been converting
>> > excel reports to reporting services. Some of the reports are over 50
>> > pages. I've been really pleased with creating these reports in
>> > reporting services. The reports look much better than the original
>> > Excel reports, and from start to finish it only take a few minutes to
>> > generate a pdf, which we send to our clients.
>> > Putting the reports online or in a windows application with user
>> > interactivity would have been icing on the cake. I can change some of
>> > my reports to have a drill down, but several of the reports need to
>> > show all the detail together. It's too bad reporting services only
>> > supports an HTML version for the web. HTML doesn't display the
>> > footers, page breaks, and page numbering like the pdf files. It also
>> > does a post back when paging through the report, which is really slow
>> > for a report like mine.
>> > Interactive reports would have been awesome for my reports, but
>> > they're just too big. You said 2008 engine will be much faster. This
>> > will be great for a windows application. Do you know if 2008 will
>> > have a different format than HTML for the web? I haven't found much
>> > information on reporting services for 2008.- Hide quoted text -
>> - Show quoted text -
> I know you can export in those different formats, but can you display
> the reports in a different format other than HTML on the web? HTML
> doesn't display correctly and you have to post back to the server to
> move through the pages of the document.
> Billy
>|||On Aug 3, 10:03 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
wrote:
> Sure. When you request the rendering you can specify the format. Plenty of
> people go right to PDF (HTML is much faster currently).
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> <billyburd...@.gmail.com> wrote in message
> news:1186175875.359497.281210@.g4g2000hsf.googlegroups.com...
>
> > On Aug 1, 11:26 am, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
> > wrote:
> >> You can render however you want (html, pdf, excel). If you do PDF that
> >> will
> >> show in the browser. In particular PDF will be much much faster (I've
> >> been
> >> promised, I haven't seen). So your reports can be displayed in your VB
> >> app
> >> with PDF and you will/should see substantial performance improvements
> >> with
> >> 2008.
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >> <billyburd...@.gmail.com> wrote in message
> >>news:1185982595.638219.275480@.19g2000hsx.googlegroups.com...
> >> > On Jul 26, 4:42 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
> >> > wrote:
> >> >> The rendering engine is the same in VS 2005 development environment as
> >> >> that
> >> >> on the server (this was not true in 2000 which is why sometimes you
> >> >> would
> >> >> see some small differences). However, VS 2005 caches data. That can
> >> >> account
> >> >> for some of the issues. Another issue is network transmission time.
> >> >> But,
> >> >> the
> >> >> main time difference is when you preview in VS you are previewing html
> >> >> which
> >> >> is many times faster than PDF or other types of formats.
> >> >> RS shines at providing data quickly to the user. By deciding you want
> >> >> to
> >> >> present a book (or an electronic paper report) you are not taking
> >> >> advantage
> >> >> of the strengths of RS. The best way to design reports is to present
> >> >> 10-20
> >> >> pages to the user (or less). Make extensive use of drill through
> >> >> (links
> >> >> that
> >> >> pull up additional detail reports).
> >> >> They are re-writing the rendering engine for 2008 and expect PDF (and
> >> >> other
> >> >> formats) that are slow today to be quite a bit faster.
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >> <billyburd...@.gmail.com> wrote in message
> >> >>news:1185484622.910356.290840@.b79g2000hse.googlegroups.com...
> >> >> > I've been building reporting services reports for the last 6 months,
> >> >> > and we just got our reporting services server last week. I've
> >> >> > started
> >> >> > deploying my reports to the reporting server, and I'm disappointed
> >> >> > in
> >> >> > the speed of the reports in a VB.Net windows application. I'm
> >> >> > running
> >> >> > the reports in remote processing mode (not local).
> >> >> > The reports generate much slower than they do in Visual Studio. The
> >> >> > reports generate REALLY slow, if the reports are viewed in print
> >> >> > layout mode. I'd like to be able to use the print layout view, so
> >> >> > the
> >> >> > report will display the footers, page breaks, and page numbering
> >> >> > correctly.
> >> >> > The reports run great in Visual Studio. Does anyone have any
> >> >> > suggestions to make the reports in a VB.Net windows application run
> >> >> > like they do in Visual Studio? Can anyone explain why the
> >> >> > performance
> >> >> > is so different between the two? Why does rendering the report in
> >> >> > print layout mode so much slower in VB vs. Visual Studio? Or should
> >> >> > it be the same?
> >> >> > I'm using reporting services 2005. Our reporting services server is
> >> >> > running on a separate server than our SQL database.- Hide quoted
> >> >> > text -
> >> >> - Show quoted text -
> >> > Thanks for your response. For the last 6 months I've been converting
> >> > excel reports to reporting services. Some of the reports are over 50
> >> > pages. I've been really pleased with creating these reports in
> >> > reporting services. The reports look much better than the original
> >> > Excel reports, and from start to finish it only take a few minutes to
> >> > generate a pdf, which we send to our clients.
> >> > Putting the reports online or in a windows application with user
> >> > interactivity would have been icing on the cake. I can change some of
> >> > my reports to have a drill down, but several of the reports need to
> >> > show all the detail together. It's too bad reporting services only
> >> > supports an HTML version for the web. HTML doesn't display the
> >> > footers, page breaks, and page numbering like the pdf files. It also
> >> > does a post back when paging through the report, which is really slow
> >> > for a report like mine.
> >> > Interactive reports would have been awesome for my reports, but
> >> > they're just too big. You said 2008 engine will be much faster. This
> >> > will be great for a windows application. Do you know if 2008 will
> >> > have a different format than HTML for the web? I haven't found much
> >> > information on reporting services for 2008.- Hide quoted text -
> >> - Show quoted text -
> > I know you can export in those different formats, but can you display
> > the reports in a different format other than HTML on the web? HTML
> > doesn't display correctly and you have to post back to the server to
> > move through the pages of the document.
> > Billy- Hide quoted text -
> - Show quoted text -
I'll do some research on how to do this. Thanks for all your
responses.
Billy