[Solved] Grid causes a database locking issue

[Robert Munoz]

 

We are using the grid with AJAX binding and a SQL server 2008 back-end (.Net 4, MVC 2 and LINQ to Entities in between) and are encountering database locking issues when we put the grid page(s) under load.

 

Is it possible to force the grid query to use an isolation level of ReadUncommitted?

 

Similar to this:

using (TransactionScope scope = new TransactionScope(TransactionScopeOption.Required, new TransactionOptions { IsolationLevel = System.Transactions.IsolationLevel.ReadUncommitted })) {

     //Run the query

}

 

We are not changing data directly from the grid so we don't mind if we encounter the odd phantom record.

 

Would could evaluate our LINQ before sending it to the GridModel but we don't want to be retrieving large result sets from the database and passing them around the web server. We'd prefer to let the GridModel retrieve just the data for the current grid page - but without taking out a database lock.

Thanks

[Atanas Korchev]

Hello Robert Munoz,

The grid does not perform any database communication actually. It only applies linq expressions to the  IQueryable which the developer has provided (to do paging, sorting, filtering or grouping). Setting isolation levels should happen when you retrieve the IQueryable for the first time.

Regards,
Atanas Korchev
the Telerik team