I have a windows form that has two DataGridViews (DGVs) that will hold 25,000+ records and 21 columns each. I have successfully loaded each with the data from the DB using a DataAdapter and then I tried simply filling the DGVs using for loops. Each method took roughly the same amount of time. The first time the data is filled into the DGVs it takes too long (7+ mins), and then the subsequent times the time is much more reasonable (~30 secs). So my question is, what is the best way to load a DGV with a large amount of data that will take on average <= 1 min? I really like the functionality of DGVs, but if push comes to shove I am willing to use a different technology, even if it means giving up some of that functionality.
-
5Do you know about virtual mode? You wouldn't load all of the data. The DGV will tell you "I need records 146-203" and you fetch only those rows. http://msdn.microsoft.com/en-us/library/15a31akc.aspx – Jonathan Aug 26 '10 at 23:10
-
Thanks Jonathan!! That sounds like what I need. However, I have one question. The next step in the app is to compare the two DGVs. Will I still have access to the entire dataset when comparing them programmatically? – Bkins Aug 27 '10 at 00:04
6 Answers
There are basically 3 ways to display data in a DataGridView
Create the rows manually in a loop, as you are currently doing: as you have noticed, it's very inefficient if you have a lot of data
Use the
DataGridView
's virtual mode, as suggested by Jonathan in his comment: the DGV only creates as many rows as can be displayed, and dynamically changes their contents when the user scrolls. You need to handle theCellValueNeeded
event to provide the required data to the DGVUse databinding: that's by far the easiest way. You just fill a
DataTable
with the data from the database using aDbDataAdapter
, and you assign thisDataTable
to the DGV'sDataSource
property. The DGV can automatically create the columns (AutoGenerateColumns = true
), or you can create them manually (you must set theDataPropertyName
of the column to the name of the field you want to display). In databound mode, the DGV works like in virtual mode except that it takes care of fetching the data from the datasource, so you don't have anything to do. It's very efficient even for a large number of rows

- 286,951
- 70
- 623
- 758
If you have a huge amount of rows, like 10 000 and more,
to avoid performance leak - do the following before data binding:
dataGridView1.RowHeadersWidthSizeMode = DataGridViewRowHeadersWidthSizeMode.EnableResizing;
//or even better .DisableResizing.
//Most time consumption enum is DataGridViewRowHeadersWidthSizeMode.AutoSizeToAllHeaders
dataGridView1.RowHeadersVisible = false; // set it to false if not needed
after data binding you may enable it.
-
1Man i know its so late to reply but after struggling for almost a week i landed up in this thread n setting as you told solved my issue...live long :) – TheSacredKiller Apr 05 '20 at 17:41
-
still relevant in 2021... not autosizing columns is a big time saver..thank you – MX313 Nov 02 '21 at 15:14
I think you can use DataReader method instead of DataAdapter. DataReader is very efficient oneway component, because it's only reading data from the source, and you can fill a data table with looping.

- 61
- 1
- 1
Try to use a DataTable. Fill it. Then use a DataView. Assign it to the DataGridView DataSource.
//DataView dataView = new DataView(dataTable);
//this.Grid.DataSource = dataView;
You will get very SMALL response times for big files (25000 records and 21 columns in a sec). My template program took 7 sec to load 100 000 Rows * 100 Columns {with stupid contents -> row number as string}

- 14,889
- 11
- 39
- 70

- 41
- 1
-
I just tested this using 10 columns, 6753 rows and it took 2:03.9174603 6735. The form that I am using is bare bones, only other control on the form is a button to initially fill the datagridview. – dmoore1181 Mar 06 '15 at 15:01
-
Please add How much time it took with the change ("DataView") and without it. so we can compare how much was the difference that it actually gave. – AL - Lil Hunk May 30 '17 at 21:14
this solved my problem:
array<DataGridViewRow^>
^theRows = nullptr;
if (DG->Rows->Count == 0)//First Compilation
{
int NUMROWS = xxx;
theRows = gcnew array<DataGridViewRow^>(NUMROWS);
for (int nr = 0; nr < DRH->Count; nr++)
theRows[nr] = gcnew DataGridViewRow();
//Do not remove the two following
DG->Rows->AddRange(theRows);
DG->Rows->Clear();
}
else //Update
{
theRows = gcnew array<DataGridViewRow^>(DG->Rows->Count);
DG->Rows->CopyTo(theRows, 0);
DG->Rows->Clear();
}
for(int nr=0;nr<theRows->Length;nr++)
{
theRows [nr]->SetValues("val1", "val2");
}
DG->Rows->AddRange(theRows);

- 10,882
- 11
- 60
- 114

- 11
- 1
- 1
- 5
I'm not sure this is quite what you're asking, but I like to create a subset of data to intitially load, and then include search functionality. This is very easy to do using visual studio 15 and DataSources / data sets. In solution explorer, open your dataset.xsd file. It will be named DataSet.xsd Go to the Data Table in question. Right-click, and add a query. One thing I commonly do is just add "TOP 1000" to my query. So, select * from mytable becomes select TOP 1000 * from mytable
Finally, double-click on your form to find your _load method, and alter the "Fill" to use your new query. This might be best demonstrated with an example:
The first line of code that I commented out is what Vis Stud created by default. The second is the one I added, which will get only the top 1000 records.
private void Form_Customers_Load(object sender, EventArgs e)
{
// TODO: This line of code loads data into the 'stage2DataSet.customers' table. You can move, or remove it, as needed.
/* this.customersTableAdapter.Fill(this.stage2DataSet.customers); */
this.customersTableAdapter.FillBy_Top_1000(this.stage2DataSet.customers);
}

- 101
- 3
-
I really am against use of untyped DataSets. a) That query will work, but when you update your DataSets at a later time, especially as your database grows and it starts becoming difficult to find the particular query in the DataSet designer, it will overwrite all your queries and reset to default ones only. So you have to keep recreating those user-defined queries. b) They also require you to fill the TableAdapters in every place before you can code against the data, which can be very slow. – Hannington Mambo Jun 30 '18 at 10:01