T Hoecherl
asked on
VB.net DataGridView.Fill performance
I have a VB.net program that includes a DataGridView. The binding source pulls data from a table with as many as 250,000 records in the table, depending on how many people are logged in and currently using the program. The records to display in the dgv for a given user are filtered by the machine name like this:
Me.PCTSNUGZFILTERBindingSo urce.Filte r = String.Format("MACHINE = '" & strMachine & "'")
The fill command is this:
Me.PCT_SNUGZ_FILTERTableAd apter3.Fil l(Me.SHOPF LOOR_SNUGZ .PCT_SNUGZ _FILTER)
The user will see anywhere between 6,000 and 30,000 records, depending on how many orders are in the pipeline at that time.
Initially, it was taking up to 45 seconds to load the data and display it. I tracked the bottleneck down to three processes: 2 SQL stored procedures and the dgv.fill. Each process took about 15 seconds.
I worked on the SQL stored procs and reduced the time on one of them to less than 1 second and the other to less than 5 seconds.
However, I don't know how to speed up the dgv.fill process. I have studied available postings on the internet, but I haven't found anything yet that helps me. Does anyone know of ways that I can speed up the dgv.fill process?
T
Me.PCTSNUGZFILTERBindingSo
The fill command is this:
Me.PCT_SNUGZ_FILTERTableAd
The user will see anywhere between 6,000 and 30,000 records, depending on how many orders are in the pipeline at that time.
Initially, it was taking up to 45 seconds to load the data and display it. I tracked the bottleneck down to three processes: 2 SQL stored procedures and the dgv.fill. Each process took about 15 seconds.
I worked on the SQL stored procs and reduced the time on one of them to less than 1 second and the other to less than 5 seconds.
However, I don't know how to speed up the dgv.fill process. I have studied available postings on the internet, but I haven't found anything yet that helps me. Does anyone know of ways that I can speed up the dgv.fill process?
T
ASKER
I think I explained it poorly. The table used as the data source is called PCT_SNUGZ_FILTER. It is populated by a stored procedure that uses the machine name as a parameter and pulls data from a view that consists of 3 table joins. The procedure selects every record currently in production and inserts the values of the record into the PCT_SNUGZ_FILTER table and populates a column called MACHINE with the current users machine name. When the user logs off, all records in the table with that machine name are deleted. So if there are 10,000 records in the production pipeline and I am the only one using the program, there will be 10,000 records in the table. But if 25 of us are logged on, there will be 250,000 records.
When I populate the dgv, however, I only want to see the records with my machine name in the MACHINE column. I thought about creating a temp table for each logged in user so each table would only have 10,000 records in it, following our example, but I don't know how to then make that table the data source for that user's session. As I understand it, I select a datasource assigned to the dgv and I can't make it dynamic, depending on the user.
So I can certainly write a stored procedure using the machine name as a parameter and return only the filtered rows, but what do I return them to?
T
When I populate the dgv, however, I only want to see the records with my machine name in the MACHINE column. I thought about creating a temp table for each logged in user so each table would only have 10,000 records in it, following our example, but I don't know how to then make that table the data source for that user's session. As I understand it, I select a datasource assigned to the dgv and I can't make it dynamic, depending on the user.
So I can certainly write a stored procedure using the machine name as a parameter and return only the filtered rows, but what do I return them to?
T
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Change your stored procedure to take the machine name as a parameter and only return the filtered rows.