SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSRS 2005 Report Executions times


SSRS 2005 Report Executions times

Author
Message
dvprao
dvprao
SSC-Addicted
SSC-Addicted (450 reputation)SSC-Addicted (450 reputation)SSC-Addicted (450 reputation)SSC-Addicted (450 reputation)SSC-Addicted (450 reputation)SSC-Addicted (450 reputation)SSC-Addicted (450 reputation)SSC-Addicted (450 reputation)

Group: General Forum Members
Points: 450 Visits: 151
I am trying to understand the following scenario:

There is a Report that uses 2 stored procedures to retrieve data.

The Stored Procedures when run in SSMS , with params values supplied execute and completes in under one minute.

But the same Report when Run in SSRS Report Manager takes nearly one hour or more.

Here are sample data retrieval times 4202160 , 4078955 , 3499796 in milli seconds

And worse , when you try to access the same report embedded in a Wweb Applicaiton page accessed via a menu takes another 50% more time than Native SSRS Report execution time.

What shaould I do to troubleshoot this. ? Any hints or guidance is sincerely appreciated.
Evil Kraig F
Evil Kraig F
SSC-Dedicated
SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)

Group: General Forum Members
Points: 34957 Visits: 7660
It sounds like the execution plan is changing heavily between a local call and the SSRS call. Either that or data transfer on the network is amazingly slow between those two servers.

I'd start with a profiler trace to grab the xmlplan of the call when it comes from SSRS and then compare it to the one you get from SSMS. If they match, you have a problem external to the server. If they don't, you'll have to analyze the call differences between the two.


- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions | Forum Netiquette
For index/tuning help, follow these directions. |Tally Tables

Twitter: @AnyWayDBA
dvprao
dvprao
SSC-Addicted
SSC-Addicted (450 reputation)SSC-Addicted (450 reputation)SSC-Addicted (450 reputation)SSC-Addicted (450 reputation)SSC-Addicted (450 reputation)SSC-Addicted (450 reputation)SSC-Addicted (450 reputation)SSC-Addicted (450 reputation)

Group: General Forum Members
Points: 450 Visits: 151
Thanks. Appreciate the hint.
I did a profiler and got the showplan xml files.
Yes indeed. In SSMS there is a Clustered Index scan( 28%) , where as in SSRS execution , it is using a non-clustered index and there is a key lookup loop that is 46% cost.

How to force it to scan the clustered index ?
Evil Kraig F
Evil Kraig F
SSC-Dedicated
SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)

Group: General Forum Members
Points: 34957 Visits: 7660
Typically you don't. You can add a table hint for experimentation using WITH INDEX(1) (similar to adding with NOLOCK) and see if that cures the actual problem. Don't trust the percentage costs in the execution plans, they lie like rugs. Knowing what it's doing can help though.

Are the parameters the same between your test call in SSMS and the one from SSRS? This may be a case of parameter sniffing and you possibly want to include an 'optimize for' selection in the query definition, or use other workarounds to it, such as transferring your parameters to local variables before usage.


- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions | Forum Netiquette
For index/tuning help, follow these directions. |Tally Tables

Twitter: @AnyWayDBA
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search