We have utilized a variant of Server-Side Pages, and we need to export the entire data set, instead just exporting the first 200 records.

An example of Server-Side Paging is.

1. Say you have a data set of 10000 records to display in a grid. Client-Side Paging requires that all the records are downloaded and stored in the browser and the paging is handled by the grid. But when dealing with excessively large data set, you can use the server to reduce the amount of data to be downloaded into the control.
   1. Say we have the 10000 records; your data grid page size is 10 and the current displayed page is 4. On the server, when obtaining the data to be displayed the page size and current page is including in the call to the data source within the controller. So instead of getting the entire data set your SQL will restrict the resultant will start on the 50th record and return the next 10 records.

      This allow the dataset to be query without having the load issues due to the excessive size of the resultant. This is very useful when providing a web interface for a data warehouse additionally it is a common technique.

2. Now suppose we need to export that entire set of data. There are only 10 records in the grid structure, the other records are not available. Could Telerik to be enhanced to account for this scenario. So that the data export can include a method to export complete data set whether dealing with the Server-Side Paging or not