I am attempting to increase the performance of the Radsheduler by pulling only those appointments within the visible range. The control is extremely slow if I do not. I have recurring appointments that span 3 months and if I navigate past the original appointment and retrieve the appointments from my database based on the visible range I lose the recurring appointments. If I expand the range to overlap the original appointment I get all the recurring appointments. Is there a way to query via linq using the visible start and end range and still get the recurring appointments without having to increase the range which defeats the purpose of using only the visible range? The documentation below contradicts itself from one sentence to the next. If I utilize a great deal of recurring appointments them I stuck with poor performance? Getting all data from the database is really not an option because the control performs terribly.
From Documentation:
You can use the RadScheduler properties to optimize your query. For example, the VisibleRangeStart and VisibleRangeEnd properties can be used to limit the number of records that the query retrieves. Recurring appointments are evaluated in-memory, however, so they should be always retrieved regardless of VisibleRangeStart and VisibleRangeEnd.
From Documentation:
You can use the RadScheduler properties to optimize your query. For example, the VisibleRangeStart and VisibleRangeEnd properties can be used to limit the number of records that the query retrieves. Recurring appointments are evaluated in-memory, however, so they should be always retrieved regardless of VisibleRangeStart and VisibleRangeEnd.