I have a stored procedure that I've tested over and over again in SQL Server Management Studio and it works fine, returning results in roughly 3 seconds; however, when I add the Stored Procedure as the Query Type for a new DataSet in Report Builder and attempt to, either run the report or execute the SP through the built-in Query Designer the execution call times-out. I haven't even used the dataset yet in any area within the report (Tablix's or Charts).
I've made sure that the Data Sources credentials are setup properly and even tested the connection to the DB and received a successful connection statement.
I have the Dataset Time out property set to 0 which should mean no timeout. Clearly, the timeout I'm receiving is being handled by the SQL Server rather than the Report Builder in this particular case.
What would make the Stored Procedure execute properly and efficiently (speed-wise) when executed from the server, but time-out when executed from Report Builder?
I'm running 2008 R2.
Please help! Thanks in advance.
Most time-out errors occur during query processing. If you are encountering time-out errors, try increasing the query time-out value. Make sure to adjust the report execution time-out value so that it is larger than the query time-out. The time period should be sufficient to complete both query and report processing.
Thanks
Venky
Collected from the Internet
Please contact [email protected] to delete if infringement.
Comments