Wednesday, March 7, 2012

RS Layout and Preview Tab - SLOW

Hello, I have been working with Reporting Services for several months and really like it. I am using Visual Studio .net for developing reports. I have noticed a long delay when changing between the 'Layout Tab' and the 'Preview Tab'. The delay is between 10 and 15 seconds which may not seem like much but adds up over time. Does anyone know if this is an issue with RS or the .net environment? Are there settings to change to make this change quicker? I know each time you change from one tab to another a new .rdl file has to be built but I have witnessed several demos from Microsoft and their setups appear to be instantaneous. Any ideas would be helpful!!! Thanks, Dave
--
Message posted via http://www.sqlmonster.comIf you report has paramters then you are just seeing building the report, no
parameters then it is also executing the report. Once it has executed it
though, it then caches the data (look in your directory and you will see
reportname.rdl.data). Even a pretty complicated report takes only a couple
of seconds to build the report. Ususally a second or less. How much RAM do
you have. It seems to me like you might be getting some thrashing going on.
"David Cymbala via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:b664fdd433c94909a44639deb1c12d91@.SQLMonster.com...
> Hello, I have been working with Reporting Services for several months and
really like it. I am using Visual Studio .net for developing reports. I
have noticed a long delay when changing between the 'Layout Tab' and the
'Preview Tab'. The delay is between 10 and 15 seconds which may not seem
like much but adds up over time. Does anyone know if this is an issue with
RS or the .net environment? Are there settings to change to make this
change quicker? I know each time you change from one tab to another a new
.rdl file has to be built but I have witnessed several demos from Microsoft
and their setups appear to be instantaneous. Any ideas would be helpful!!!
Thanks, Dave
> --
> Message posted via http://www.sqlmonster.com|||Thank you for your response. My client station is a 3Ghz Pentium with 256 megs of ram. I consistently see this delay regardless of whether the report has parameters or not. The delay occurs before the 'Processing Report...' dialogue appears. The same query in query analyzer takes fractions of a second to complete. Any additional insight would be greatly appreciated. Thanks, Dave
--
Message posted via http://www.sqlmonster.com|||That is faster than my machine but I have 512MB more RAM than you. Besides
adding RAM if you can, how do you have your data source setup, is it a
shared datasource or are you doing it per report. I use shared data source.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"David Cymbala via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:8c91c4a235784ec4b6a9e8de4b04f06d@.SQLMonster.com...
> Thank you for your response. My client station is a 3Ghz Pentium with 256
megs of ram. I consistently see this delay regardless of whether the report
has parameters or not. The delay occurs before the 'Processing Report...'
dialogue appears. The same query in query analyzer takes fractions of a
second to complete. Any additional insight would be greatly appreciated.
Thanks, Dave
> --
> Message posted via http://www.sqlmonster.com|||I am using a shared datasource. I wish I knew if increasing memory would solve this problem before upgrading. Thanks for your responses. Dave
--
Message posted via http://www.sqlmonster.com|||I don't know what else it could be. I have a slower computer and don't see
this. Do you have SQL Server and IIS locally as well? If so then SQL Server,
IIS, VS is a lot in 256 MB. Bring up task manager and see what is going on,
you should be able to see memory usage.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"David Cymbala via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:d3fba556874c4760b739831eb8e33089@.SQLMonster.com...
> I am using a shared datasource. I wish I knew if increasing memory would
solve this problem before upgrading. Thanks for your responses. Dave
> --
> Message posted via http://www.sqlmonster.com

No comments:

Post a Comment