>As I am looking at a couple of examples of implementing paging in a gridview (below is one url of an article) it seems to me that the way it is done is that on Every Next Page click the entire dataset (to which gridview is bound) is created. That is, every time user clicks to go to the next page, there is a call to DB and dataset is Fillled. Aside from visual (maybe) perception of dealing with smaller number of records, where is the processing saving of this method?
>
>Here is the article on which I base my understanding:
>http://www.dotnetgallery.com/kb/resource12-How-to-implement-paging-and-sorting-in-aspnet-Gridview-control.aspx.aspx
>
>I thought that the paging would get the entire dataset One Time and then simply display the rows of the dataset according to the user paging.
>
>What am I not getting?

The results of the query need to be cached if you want to use them again without reissuing the query. If you use a SqlDataSource (http://msdn.microsoft.com/en-us/library/dz12d98w%28v=vs.90%29.aspx), it can cache the results automatically. Otherwise, if performance is an issue, you may need to implement your own caching or paging functionality. If you are using SQL Server 2012, it now has OFFSET and FETCH clauses that you can use for paging (http://dbadiaries.com/new-t-sql-features-in-sql-server-2012-offset-and-fetch).