Is there a limit in the number of registers we can bind to a RadScheluder datasource?

[Rafael]

Hello everybody,

I make this question because I’m experienced problems in a web agenda managed by RadScheduler. When I bind 5000 registers everything goes fine, but with 60000 I experience a Sys.WebForms.PageRequestManagerServerErrorException.

I’m working with OpenAccess and the access to the database is very fast and I obtain finally a IList<Appointement> object, that I assign to a RadSecheluder datasource. Debugging the program I can see that the RadScheduler is recovering every object attribute, object by object, before show the agenda, and in that step is when the error occurs (with large number of registers only).

Thank you in advance.

[T. Tsonev]

Hi Rafael,

Working with such great number of appointments will indeed lead to performance problems. Our recommendation is to filter the appointments, so you only bind to the appointments that are actually visible. You can see such demo here:

http://demos.telerik.com/aspnet-ajax/scheduler/examples/optimizedqueries/defaultcs.aspx

The demo shows how to do this with a regular data source, but you should be able to apply this idea to OpenAccess as well. I hope this helps.

Regards,
Tsvetomir Tsonev
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

[Rafael]

Thank you for your replay,

You’re absolutely right. I have implemented a solution using the way your link indicates, and now web goes clearly faster.

I have these figures: 34 appointments / day, 128 app. / week, 434 app. / month.

First start in day view consumes 2.5 seconds.  Switch between views 3.2 seconds. (2MB DSL / IE8 / Windows 7).

Best regards.