You are talking about the Connect Timeout which can be set in the Connection String.
What is at issue here is the
CommandTimeout which is set as a property of an individual .NET
SqlCommand object. In an effort to solve the problem of my reports timing out after 30 seconds, I set the Connect Timeout in my Connection Strings to 600 seconds (10 min), and also provided implemented the IReportServiceClientFactory with the following code
.
Neither of these have provided a solution.
Now I'm only guessing, but it appears the only timeout left which is set to 30 seconds by default is the
SqlCommand.CommandTimeout. Many of my reports are timing out exactly at 30 seconds, and without the ability to set this value I cannot determine without a doubt that this is the problem. I assume that at some point in the ReportService code there is a SqlCommand object being created, or some similar object that contains this CommandTimeout property that can be set. If I am correct, and this is the valuie that I must change in order for my reports to run, the inability to change the value will render Telerik Reporting useless for our development needs. We are developing an application for the State of Nevada where we deal in database tables that have in excess of 1,000,000 records. I really have no desire to switch reporting products, and it will seriously affect our development schedule if we are forced to, however if I cannot resolve this issue quickly, I will have no choice.
Please do all you can to provide a way to set this value, or help me find the true cause of this timeout.
Thank you,
Steve