Performance with DataSet: suggestions for best practices? -- dotnet windows forms databinding

dotnet windows forms databinding : Performance with DataSet: suggestions for best practices?

Chris Zopers
3/25/2005 1:47:39 AM

Hello,

I've developed a lot of database-systems in Microsoft Access. Now I'm
going to develop a large system in VB.NET. Before I start, I'm testing
some performance differences between MS Access and VB.NET. When I
connect to a large table (more than 100.000 records) from a database
with MS Access, everthing works just fine and the performance is very
good. When I load the same table in a DataSet in my VB.NET application,
it takes a very long time to load that table.

I'd like to know from experiences VB.NET programmers: what is the best
way to work with data? DataSets are all in-memory, so won't that take a
lot of the computers memory? And that's probably why the loading of a
large table takes so long. Does anyone have suggestions?

Greetings,
Chris.

*** Sent via Developersdex http://www.developersdex.com ***

David Lei
4/5/2005 5:51:46 PM

Unless you need to operate on all 100,000 records, don't load them
into a DataSet all at once.

Try to break them up and load them 20 at time or allow user to
search for a record.

David

[quoted text, click to view]

JSantora
4/6/2005 9:53:13 PM

Just from a usability perspective...what's a user going to do with
100,000 records? They can't be just browsing around like my wife does
in a shopping mall, they must have something in mind. Ask them what
they are looking for, even if that changes from day to day, they should
be able to say..."the March invoices", the "Open Orders" or "some
customer named 'Acme something'". from there you can pass some
parameters to a stored proc, and hopefully return the 6 records they
need. You're program will look soooo intelligent.
good luck
john

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet windows forms databinding

home · blog · groups

Questions? Comments? Contact the dn