Saving an ADO Resultset to disk, then opening it later !

[davidsheardown]

(using ADO 2.5)<br>OK, I have a situation where where are creating an ADO resultset daily (approx 5,000 recs) and saving the resultset to disk.<br><br>At the end of the month, we &quot;concatinate&quot; each days data into one big resultset (i.e: re-reading each day one at a time).&nbsp;&nbsp;The idea was to read a record from the saved ADO file (using ADTG), and then write to our own created ADO resultset.<br><br>This works, but the MEMORY usage is amazing !&nbsp;&nbsp;It seems to load all rows into memory, before finally writing the new combined resultset !<br><br>DOES ANYONE HAVE ANY SUGGESTIONS ON HOW BEST TO ACHIEVE THE ABOVE ??????

 

[Karl Blessing]

in ADO there should be a Page property, you could just grab pages at a time. Rather than the whole recordset at a time. <p>Karl<br><a href=mailto:kb244@kb244.com>kb244@kb244.com</a><br><a href=

http://kb244.com>

</a><br>Experienced in : C++(both VC++ and Borland),VB1(dos) thru VB6, Delphi 3 pro, HTML, Visual InterDev 6(ASP(WebProgramming/Vbscript)<br>

http://www.brainbench.com/transcript.jsp?pid=629151

 

[dellyjm]

I once saved a recordset 80000+ records on from a table with 127 columns. <br>Memory usage was great, i did it on a machine with 64MB RAM though. <br>I'm not sure how many columns your table has, but what you probably coud do is save the recordset in about 5 parts (5 separate recordsets) and then work with it that way...problems should be solved...not much extra coding.

 

[davidsheardown]

Thanks.&nbsp;&nbsp;The resultset is obtained from various previously saved recordsets (I think thats the problem).&nbsp;&nbsp;So I am reading upto 31 saved recordsets, each of around 4-5000 records, and building one big recordset to then be used to return to an ASP page.&nbsp;&nbsp;I think one idea is to use the cache/page property of the recordset to see if I can optimise ??<br><br>Thanks for your reply.