For additional information on the logic behind this example, you can review the description tag. It contains all the related information on the events which are raised when dragging a row. Once you acquaint yourself with the events regarding this logic, you can handle the setup as per your requirements - if you are using a different datasource, or want to cache the data, or anything else. Regardless of these differences, the core logic/events remain the same. The client side events allow you to handle logic prior to persisting the change in the database - identify the row/target element, or cancel out the event.
The server side event allows you to handle the actual persistence of the item in the database.
I hope this information helps.
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.