Visual Studio .NET - How do I bind a large dataset to DataGridView

Hi,

I have a dataset that contains over one million records,  currently I am loading the dataset and then setting the DataSource property of my DataGridView to the datset, my DataGridView takes about 5 mins to load,  2.5 mins is spend waiting on the dataset to get populated and the other 2.5 mins on the DataGridView to load.  I have been doing some research and it appears that I have to put the DataGridView into virtual mode,  however what am I then suppose to do with my DataSet,  are there any examples of something like this being done, as I am sure it must be a very common task.  My DataGridView needs to also support the adding, deleting and editing of records.

Thanks in advance,

you can use paging or

You can load only the necessary data by using DataAdpter.Fill below way

  myAdapter.Fill( ds , startRecord , int.Parse( PageSize.Value ) , "Products");
To check more about this take a look BuildGrid method of  link

http://www.mastercsharp.com/article.aspx?ArticleID=76&&TopicID=2

Just check out this article on "Binding Data To The User Interface", it tells you the various data binding modes and also how to handle complex data binding with a small case study,

Simple Data Binding
Complex Data Binding
One-way and two-way Data Binding
The BindingContext object
The Data Form Wizard

http://blogs.wdevs.com/a.Panahy/archive/2005/02/08/2254.aspx

just some links FYI,

DataSets vs. Collections

http://msdn.microsoft.com/msdnmag/issues/05/08/CuttingEdge/default.aspx

hope it helps!

use Custom Paging in ASP.NET 2.0 with SQL Server 2005 , coz this will bind only 10 or some no of records to grid at a time not comelete data so this will help u in loding gridview

check out complete example here

http://aspnet.4guysfromrolla.com/articles/031506-1.aspx

It is not a good practice to bind a lasrge dataset to a grid control. Practically there is less probability that a user will to to every page of you grid. A better option will be to fetch records for pages where you think proablility of user interaction is high e.g. first 10 pages recordes containing recent data. If user wants to visit page number 15 then you can fetch data for page number 11 to 20.(User could be looking for some records). I mean to sa that in case of large data  you have to guess user's action and to code accordingly(little complex coding).

Rajesh Madhukar