Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can any one suggest me how to handl

Status
Not open for further replies.

shaileng

Programmer
May 15, 2003
10
US
Can any one suggest me how to handle very large recordsets (lets say 10 lac records) using ADO which highest performance. I am very well aware of the ADO optimising properties. How ever I want to know if there are any more alternative ways.

I will be very thankful if any one can provide the links also actually I tried searching net but could not find it out.

Regards
 
There is not likely to be much response to this post:
Are you actually having specific performance issues?
Tell us what they are and someone may be able to help.

 
What are you doing with the recordset?

Are you trying to display the results of the recordset or is it remaining in memory?

What kind of database are you using?

What is the setup, all local, Client/Server, etc, etc?

Have you added parameters to reduce the size of the recordset as much as possible?



Take Care,

zemp
 
Hi friends,

I am developing a control which will act like a "find form". Where all the records will be displayed and then depending on user choice functions like sort, filter etc. will be carried out.

Now I can use recordset object for this which will fetch the records initially from database and then will work it for filtering, sorting etc. How ever as the # of rows grows the performance deteriorates.

I want some help on doing this is seconds. Can XML be helpful ? How ? Most important thing to put here is concurrency, simultenious updates, inserts wont be a "MUST TO HAVE" functionality.

I believe XML will be helpful and sorting, filtering etc are just test based and hence no need to implement the code using traditional recordset method.

Can you help?
 
Look into using a paged recordset. It will load only the records that a grid can display and load more 'pages' as the user scrolls the grid. This way the time needed to load the grid is not as noticable as it occurs in many small intervals rather than one large one. See the link below.



Take Care,

zemp

"If the grass looks greener... it's probably because there is more manure."
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top