I am sorry to hear that you are experiencing issues when performing queries with Telerik Data Access.
I have tried and failed to reproduce the same command timeout in our test suite. The configured value (6000 seconds) was properly set to the underlying DbCommand
Are you using a different backend configuration in other places in your application?
If you are you should know that there is an internal Database object instance that is created the first time you have created a OpenAccessContext
instance and the backend configuration provided at that point is the one that will be used for the whole lifetime of the Database object.
One easy way to fix the issue in that case is just to apply the configuration during your application start-up.
Another option is to have two separate Database instances running in parallel and using different configurations - one with original start-up settings and one with new report-friendly. One easy way to create a new Database object is to use the following code:
// extend your context class via a partial class
cacheKey, BackendConfiguration backendConfig)
(connectionStringName, cacheKey, backendConfig, metadataSource)
// in your query method use the new constructor
BackendConfiguration fromCodeConfiguration = EntitiesModel.GetBackendConfiguration();
(var context =
// TODO: perform your query
This code snippet will result in creation of a new Database object instance with the specified configuration. The cacheKey
in the example) will allow you to reuse the second Database instance the next time you are using this code.
Please note that Database object creation is a costly operation and will result in higher memory consumption. You should fine the best balance between keeping more than one instance active and creating/disposing the extra one(s) after you are done with them.
In order to dispose your existing database instance you can use OpenAccessContext.DisposeDatabase(string)
method as described on the bottom of this page
If you are still having trouble with command timeout errors while running your query, please let us know and we will arrange a way for you to send us your model and the query code if it is possible.
OpenAccess ORM is now Telerik Data Access
. For more information on the new names, please, check out the Telerik Product Map