We have a SQL Server 2005 application that we deploy most of the time on SQL
Express, not full blown SQL. We have a Development box here (2 CPU XEON
with 4GB RAM) that has the Developer Edition and an instance of SQL Express
installed. If I run the same reports, with the same data, but one on the
developer edition and one on the Express Edition, there is a SIGNIFICANT
performance difference. This is a 1-page report - nothing huge, and it
renders in 2-3 seconds on Developer edition, but consistantly takes 15-20
seconds on the Express Edition.
I know SQL Express has a 1GB RAM limit, and a 1-CPU limit, but are there any
settings or anything that I can do to bring this closer to the full blown
SQL Version. This performance killing me onsite...
Any thoughts?
Thanks,
Markhave you identify if the problem is related to RS or SQL?
Does the SQL query is slower on the express edition? or the query takes the
same amount of time?
if the difference is here, then you have to play in the query and the
indexes to optimize it for the Express edition.
"Mark Essex" <messex@.netalytics.com> wrote in message
news:eyZTzG35HHA.980@.TK2MSFTNGP06.phx.gbl...
> We have a SQL Server 2005 application that we deploy most of the time on
> SQL Express, not full blown SQL. We have a Development box here (2 CPU
> XEON with 4GB RAM) that has the Developer Edition and an instance of SQL
> Express installed. If I run the same reports, with the same data, but one
> on the developer edition and one on the Express Edition, there is a
> SIGNIFICANT performance difference. This is a 1-page report - nothing
> huge, and it renders in 2-3 seconds on Developer edition, but consistantly
> takes 15-20 seconds on the Express Edition.
> I know SQL Express has a 1GB RAM limit, and a 1-CPU limit, but are there
> any settings or anything that I can do to bring this closer to the full
> blown SQL Version. This performance killing me onsite...
> Any thoughts?
> Thanks,
> Mark
>|||The query is 'instant' (less than a second) on both SQL Instances, so I
would say that this is an RS issue, not a SQL issue.
"Jeje" <willgart@.hotmail.com> wrote in message
news:2645D59B-223F-4F18-9712-AFF641F24C77@.microsoft.com...
> have you identify if the problem is related to RS or SQL?
> Does the SQL query is slower on the express edition? or the query takes
> the same amount of time?
> if the difference is here, then you have to play in the query and the
> indexes to optimize it for the Express edition.
>
> "Mark Essex" <messex@.netalytics.com> wrote in message
> news:eyZTzG35HHA.980@.TK2MSFTNGP06.phx.gbl...
>> We have a SQL Server 2005 application that we deploy most of the time on
>> SQL Express, not full blown SQL. We have a Development box here (2 CPU
>> XEON with 4GB RAM) that has the Developer Edition and an instance of SQL
>> Express installed. If I run the same reports, with the same data, but
>> one on the developer edition and one on the Express Edition, there is a
>> SIGNIFICANT performance difference. This is a 1-page report - nothing
>> huge, and it renders in 2-3 seconds on Developer edition, but
>> consistantly takes 15-20 seconds on the Express Edition.
>> I know SQL Express has a 1GB RAM limit, and a 1-CPU limit, but are there
>> any settings or anything that I can do to bring this closer to the full
>> blown SQL Version. This performance killing me onsite...
>> Any thoughts?
>> Thanks,
>> Mark
>>|||what is the connection string used by the report?
and does RS and SQL are on the same server?
"Mark Essex" <messex@.netalytics.com> wrote in message
news:eoyjDAJ6HHA.4880@.TK2MSFTNGP03.phx.gbl...
> The query is 'instant' (less than a second) on both SQL Instances, so I
> would say that this is an RS issue, not a SQL issue.
> "Jeje" <willgart@.hotmail.com> wrote in message
> news:2645D59B-223F-4F18-9712-AFF641F24C77@.microsoft.com...
>> have you identify if the problem is related to RS or SQL?
>> Does the SQL query is slower on the express edition? or the query takes
>> the same amount of time?
>> if the difference is here, then you have to play in the query and the
>> indexes to optimize it for the Express edition.
>>
>> "Mark Essex" <messex@.netalytics.com> wrote in message
>> news:eyZTzG35HHA.980@.TK2MSFTNGP06.phx.gbl...
>> We have a SQL Server 2005 application that we deploy most of the time on
>> SQL Express, not full blown SQL. We have a Development box here (2 CPU
>> XEON with 4GB RAM) that has the Developer Edition and an instance of SQL
>> Express installed. If I run the same reports, with the same data, but
>> one on the developer edition and one on the Express Edition, there is a
>> SIGNIFICANT performance difference. This is a 1-page report - nothing
>> huge, and it renders in 2-3 seconds on Developer edition, but
>> consistantly takes 15-20 seconds on the Express Edition.
>> I know SQL Express has a 1GB RAM limit, and a 1-CPU limit, but are there
>> any settings or anything that I can do to bring this closer to the full
>> blown SQL Version. This performance killing me onsite...
>> Any thoughts?
>> Thanks,
>> Mark
>>
>|||COnnection string looks like:
data source=.\installs; initial catalog = Methasoft53
RS and SQL are on the same machine.
Would the '.\installs' cause issues, meaning should I put the MACHINE NAME
in there, instead of using the 'dot' notation? Maybe a 'lookup' time issue?
Thanks,
Mark
"Jeje" <willgart@.hotmail.com> wrote in message
news:6C308FB1-6A82-440F-9746-8BED264C9313@.microsoft.com...
> what is the connection string used by the report?
> and does RS and SQL are on the same server?
> "Mark Essex" <messex@.netalytics.com> wrote in message
> news:eoyjDAJ6HHA.4880@.TK2MSFTNGP03.phx.gbl...
>> The query is 'instant' (less than a second) on both SQL Instances, so I
>> would say that this is an RS issue, not a SQL issue.
>> "Jeje" <willgart@.hotmail.com> wrote in message
>> news:2645D59B-223F-4F18-9712-AFF641F24C77@.microsoft.com...
>> have you identify if the problem is related to RS or SQL?
>> Does the SQL query is slower on the express edition? or the query takes
>> the same amount of time?
>> if the difference is here, then you have to play in the query and the
>> indexes to optimize it for the Express edition.
>>
>> "Mark Essex" <messex@.netalytics.com> wrote in message
>> news:eyZTzG35HHA.980@.TK2MSFTNGP06.phx.gbl...
>> We have a SQL Server 2005 application that we deploy most of the time
>> on SQL Express, not full blown SQL. We have a Development box here (2
>> CPU XEON with 4GB RAM) that has the Developer Edition and an instance
>> of SQL Express installed. If I run the same reports, with the same
>> data, but one on the developer edition and one on the Express Edition,
>> there is a SIGNIFICANT performance difference. This is a 1-page
>> report - nothing huge, and it renders in 2-3 seconds on Developer
>> edition, but consistantly takes 15-20 seconds on the Express Edition.
>> I know SQL Express has a 1GB RAM limit, and a 1-CPU limit, but are
>> there any settings or anything that I can do to bring this closer to
>> the full blown SQL Version. This performance killing me onsite...
>> Any thoughts?
>> Thanks,
>> Mark
>>
>>|||to see if there is a naming resolution issue, open the profiler on your
server, then run the report.
if you see the query 10 seconds after you click "view report", then there is
a name resolution issue. if you see the query in less then 1second, then
there is no naming issue and the problem is somewhere else.
but using the . (dot) should not cause name resolution issue.
but maybe there is an authentication issue.
try to use an SQL Server login instead of the windows authentication
data source=.\installs; initial catalog =Methasoft53;uid=<user>;pwd=<password>
"Mark Essex" <messex@.netalytics.com> wrote in message
news:Oqg98Rp6HHA.4584@.TK2MSFTNGP03.phx.gbl...
> COnnection string looks like:
> data source=.\installs; initial catalog = Methasoft53
> RS and SQL are on the same machine.
> Would the '.\installs' cause issues, meaning should I put the MACHINE NAME
> in there, instead of using the 'dot' notation? Maybe a 'lookup' time
> issue?
> Thanks,
> Mark
> "Jeje" <willgart@.hotmail.com> wrote in message
> news:6C308FB1-6A82-440F-9746-8BED264C9313@.microsoft.com...
>> what is the connection string used by the report?
>> and does RS and SQL are on the same server?
>> "Mark Essex" <messex@.netalytics.com> wrote in message
>> news:eoyjDAJ6HHA.4880@.TK2MSFTNGP03.phx.gbl...
>> The query is 'instant' (less than a second) on both SQL Instances, so I
>> would say that this is an RS issue, not a SQL issue.
>> "Jeje" <willgart@.hotmail.com> wrote in message
>> news:2645D59B-223F-4F18-9712-AFF641F24C77@.microsoft.com...
>> have you identify if the problem is related to RS or SQL?
>> Does the SQL query is slower on the express edition? or the query takes
>> the same amount of time?
>> if the difference is here, then you have to play in the query and the
>> indexes to optimize it for the Express edition.
>>
>> "Mark Essex" <messex@.netalytics.com> wrote in message
>> news:eyZTzG35HHA.980@.TK2MSFTNGP06.phx.gbl...
>> We have a SQL Server 2005 application that we deploy most of the time
>> on SQL Express, not full blown SQL. We have a Development box here (2
>> CPU XEON with 4GB RAM) that has the Developer Edition and an instance
>> of SQL Express installed. If I run the same reports, with the same
>> data, but one on the developer edition and one on the Express Edition,
>> there is a SIGNIFICANT performance difference. This is a 1-page
>> report - nothing huge, and it renders in 2-3 seconds on Developer
>> edition, but consistantly takes 15-20 seconds on the Express Edition.
>> I know SQL Express has a 1GB RAM limit, and a 1-CPU limit, but are
>> there any settings or anything that I can do to bring this closer to
>> the full blown SQL Version. This performance killing me onsite...
>> Any thoughts?
>> Thanks,
>> Mark
>>
>>
>
Showing posts with label slower. Show all posts
Showing posts with label slower. Show all posts
Tuesday, March 20, 2012
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
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
Friday, March 9, 2012
ReportManager is faster than ReportServer-why?
I have a report based on a stored procedure. The procedure runs very fast
from Query Analyzer. The Report I build from it runs a little slower
in "Preview", I assume due to the Grouping I am doing. It takes about 1 sec.
Then when I move it to production and view it through ReportManager is it
slower,
maybe 3 sec. I wish I knew why.
But when I run it via URL from Reportserver, like this:
http://serveripname/Reportserver?/InstructorReports/AdminListAll"
it runs a couple of seconds slower yet.
Does anyone know why the rendor time isn't the same in all 3 cases?
thanks,
VinceUsing instructions on
http://msdn.microsoft.com/library/en-us/rsadmin/htm/arp_rslogfiles_v1_88gy.asp,
you should be able to pull down ExecutionLog details for analysis. This
will let you look at each report exeuciton to see if there really is any
difference in data retrieval, processing and render times. After you use DTS
to pull down the RS Execution Log details, run SELECT * FROM
[RSExecutionLog].[dbo].[ExecutionLogs] within Query Analyzer to look for
differences.
--
-- "This posting is provided 'AS IS' with no warranties, and confers no
rights."
jhmiller@.online.microsoft.com
"thomsonDeveloper" <thomsonDeveloper@.discussions.microsoft.com> wrote in
message news:434FE938-0D45-4527-923E-8E007C930F5C@.microsoft.com...
>I have a report based on a stored procedure. The procedure runs very fast
> from Query Analyzer. The Report I build from it runs a little slower
> in "Preview", I assume due to the Grouping I am doing. It takes about 1
> sec.
> Then when I move it to production and view it through ReportManager is it
> slower,
> maybe 3 sec. I wish I knew why.
> But when I run it via URL from Reportserver, like this:
> http://serveripname/Reportserver?/InstructorReports/AdminListAll"
> it runs a couple of seconds slower yet.
> Does anyone know why the rendor time isn't the same in all 3 cases?
> thanks,
> Vince
>
from Query Analyzer. The Report I build from it runs a little slower
in "Preview", I assume due to the Grouping I am doing. It takes about 1 sec.
Then when I move it to production and view it through ReportManager is it
slower,
maybe 3 sec. I wish I knew why.
But when I run it via URL from Reportserver, like this:
http://serveripname/Reportserver?/InstructorReports/AdminListAll"
it runs a couple of seconds slower yet.
Does anyone know why the rendor time isn't the same in all 3 cases?
thanks,
VinceUsing instructions on
http://msdn.microsoft.com/library/en-us/rsadmin/htm/arp_rslogfiles_v1_88gy.asp,
you should be able to pull down ExecutionLog details for analysis. This
will let you look at each report exeuciton to see if there really is any
difference in data retrieval, processing and render times. After you use DTS
to pull down the RS Execution Log details, run SELECT * FROM
[RSExecutionLog].[dbo].[ExecutionLogs] within Query Analyzer to look for
differences.
--
-- "This posting is provided 'AS IS' with no warranties, and confers no
rights."
jhmiller@.online.microsoft.com
"thomsonDeveloper" <thomsonDeveloper@.discussions.microsoft.com> wrote in
message news:434FE938-0D45-4527-923E-8E007C930F5C@.microsoft.com...
>I have a report based on a stored procedure. The procedure runs very fast
> from Query Analyzer. The Report I build from it runs a little slower
> in "Preview", I assume due to the Grouping I am doing. It takes about 1
> sec.
> Then when I move it to production and view it through ReportManager is it
> slower,
> maybe 3 sec. I wish I knew why.
> But when I run it via URL from Reportserver, like this:
> http://serveripname/Reportserver?/InstructorReports/AdminListAll"
> it runs a couple of seconds slower yet.
> Does anyone know why the rendor time isn't the same in all 3 cases?
> thanks,
> Vince
>
Subscribe to:
Posts (Atom)