Comments on: Reporting On Data From Stored Procedures (part 1)

By: rakesh

rakesh — Thu, 25 Aug 2011 07:08:06 +0000

nice really this blog helped me out,thanx
i will take ur help for further queries

By: Edmond

Edmond — Wed, 04 May 2011 21:30:56 +0000

I just started learning about SSRS and I am extremely thankful for the step-by-step process that was posted. THANKS again.

By: Valentino Vranken

Valentino Vranken — Thu, 14 Oct 2010 05:54:19 +0000

Hi Sid,

(Sorry for not getting back to you sooner, the notification must have gotten lost in the bunch of emails during my holidays.)

I’m not aware of a setting that would influence this. But what I would probably do in such a situation is to change the slow SP. The best change would be to rewrite it so that its speed is acceptable. When that is not an option due to the specific situation, I would temporarily add a SELECT statement at the top to return some dummy records. Obviously the fields returned should match with what would be returned in normal circumstances. Then once development is finished you can put the original SP back on the server.

Best regards,
Valentino.

By: Valentino Vranken

Valentino Vranken — Thu, 14 Oct 2010 05:46:05 +0000

Thanks Frank, I’m glad it got you started!

By: Frank

Frank — Wed, 13 Oct 2010 20:04:22 +0000

I am new to SSRS. This article was extremely helpful in getting my first report (with a paramterized stored procedure) to execute. Thanks for providing this information.

By: Sid

Sid — Thu, 29 Jul 2010 13:17:57 +0000

Thanks for this — I’m finally back into SSRS after a long time.

I’m finding problems using the report designer
Report Designer in 2008 SSRS R2 times out when adding a dataset which calls a long running stored procedure. Error Message:

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

I can tell that when adding a stored procedure SSRS report designer is calling the proc.

I have captured the trace on SQL profiler and I can see the procedure call.

The stored proc on it’s own takes just over one minute to complete execution.

Is there anyway to increase (looks like 30 seconds is the default) the time out when the report designer executes this proc call when designing the report?

Thanks,
Sid

By: Reporting On Data From Stored Procedures (part 2) « A Blog for SQL Server Reporting Services (SSRS) Programmers

Fri, 11 Jun 2010 08:04:25 +0000

[...] On Data From Stored Procedures (part 2) By Valentino Vranken, on June 11th, 2010 In a previous article I announced that I would write a sequel covering how to pass multiple-value parameters from a SQL [...]