Good morning,
I'm trying to use the report viewer to display a web based report. I've already placed it on my server and was just running a couple of test inquiries with date parameters that designate what date range to display the reports, and any report > 2000 records begins to time out. I tried increasing the time out server side, and it's still giving me a problem.
My question is, is there way to prevent this issue? I am not doing a lot of sorting, filtering, or grouping. Essentially, my query is a basic Select with maybe one join in a stored procedure in SQL Server. I have used that as my data source and when I am pulling up the report the only two parameters that I give the report are a start date and end date.
The error that I am getting is always the following
[HttpException (0x80004005): Request timed out.]
Is there a way to resolve or prevent this short of just increasing the timeout to 3000 like I saw other people doing? I do not want to put too much overhead or load on the server. Another question, just to verify, Telerik does not "lock out" the records when I'm running the report viewer, correct? Since most of the reports that I have tried to run seem to take about 6 - 8 minutes to respond, I just want to ensure that I am not preventing other processes from accessing the same records.
Also, could it possibly be because of the multiple pages that the report viewer is rendering? I have it currently set to display only 22 records per page, but I forgot how to adjust that. So another question is how do I inform the report viewer that I want it to display more than 22 records per page?
Thank you in advance for your assistance.
I'm trying to use the report viewer to display a web based report. I've already placed it on my server and was just running a couple of test inquiries with date parameters that designate what date range to display the reports, and any report > 2000 records begins to time out. I tried increasing the time out server side, and it's still giving me a problem.
My question is, is there way to prevent this issue? I am not doing a lot of sorting, filtering, or grouping. Essentially, my query is a basic Select with maybe one join in a stored procedure in SQL Server. I have used that as my data source and when I am pulling up the report the only two parameters that I give the report are a start date and end date.
The error that I am getting is always the following
[HttpException (0x80004005): Request timed out.]
Is there a way to resolve or prevent this short of just increasing the timeout to 3000 like I saw other people doing? I do not want to put too much overhead or load on the server. Another question, just to verify, Telerik does not "lock out" the records when I'm running the report viewer, correct? Since most of the reports that I have tried to run seem to take about 6 - 8 minutes to respond, I just want to ensure that I am not preventing other processes from accessing the same records.
Also, could it possibly be because of the multiple pages that the report viewer is rendering? I have it currently set to display only 22 records per page, but I forgot how to adjust that. So another question is how do I inform the report viewer that I want it to display more than 22 records per page?
Thank you in advance for your assistance.
1 Answer, 1 is accepted
0
Hello Rhea,
If your reports time out you will have to increase the timeout or to redesign your reports so that they are smaller. In order to increase the timeout you have to set the CommandTimeout property of the SqlDataSource. Also please note that requiring so many records in a report already puts a lot of overhead on the server. Additionally the timeout only indicates how long the client will wait for a response from the server - smaller times are advisable in order for the application to be considered user friendly.
Telerik Reporting is using your query and is just executing it on the sql server, which means that it is no different than going to an sql manager for example and executing the same query. Please also note that usually the queries get executed in seconds - the hard work is processing and then rendering the data. Additionally since the report is very big it requires more bandwidth or time in order for the response to get back to the client.
The records are displayed according to the size of the page - if you need to show more records on a single page you will have to either make the items smaller, make the page bigger through page settings or redesign your layout.
Kind regards,
IvanY
the Telerik team
If your reports time out you will have to increase the timeout or to redesign your reports so that they are smaller. In order to increase the timeout you have to set the CommandTimeout property of the SqlDataSource. Also please note that requiring so many records in a report already puts a lot of overhead on the server. Additionally the timeout only indicates how long the client will wait for a response from the server - smaller times are advisable in order for the application to be considered user friendly.
Telerik Reporting is using your query and is just executing it on the sql server, which means that it is no different than going to an sql manager for example and executing the same query. Please also note that usually the queries get executed in seconds - the hard work is processing and then rendering the data. Additionally since the report is very big it requires more bandwidth or time in order for the response to get back to the client.
The records are displayed according to the size of the page - if you need to show more records on a single page you will have to either make the items smaller, make the page bigger through page settings or redesign your layout.
Kind regards,
IvanY
the Telerik team
HAPPY WITH REPORTING? Do you feel that it is fantastic? Or easy to use? Or better than Crystal Reports? Tell the world, and help fellow developers! Write a short review about Telerik Reporting and Telerik Report Designer in Visual Studio Gallery today!