Re: running out of memory
- From: "Val Mazur \(MVP\)" <group51a@xxxxxxxxxxx>
- Date: Wed, 6 Apr 2005 20:53:32 -0400
Hi,
First of all it is not ADO, but ADO.NET newsgroup. Maybe you should consider
using of the SQL statements on a server side inside of SP to do this rather
than looping through the records. What do you need to achieve?
--
Val Mazur
Microsoft MVP
http://xport.mvps.org
"Supertree" <Supertree@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A28DD1B8-5EB4-4F0C-A33D-14B271922291@xxxxxxxxxxxxxxxx
> Hi;
>
> I have to write custom data integrity utilities comparing files with table
> data.
> I've found that looping through an ado recordset will cause memory
> problems
> if it's a large recordset.
>
> I'm using this sort of syntax:
>
> adoRSdir = adocn.Execute(sSQL, lrecs)
>
> Do Until adoRSdir.EOF = True
> 'this loop is running out of memory
> Loop
>
> How can you monitor if you're going to run out of memory?
> What technique would be better other than narrowing the sql
> querystring result set?
>
> Thanks for your knowledge.
>
> Best Regards;
>
> Todd
>
.
- Follow-Ups:
- Re: running out of memory
- From: Supertree
- Re: running out of memory
- References:
- running out of memory
- From: Supertree
- running out of memory
- Prev by Date: Re: ConnectionTimeout is always 15 coming back from the DataLinksClass dialog
- Next by Date: Re: SQL Data Written fm ADO.NET read fm ADO
- Previous by thread: running out of memory
- Next by thread: Re: running out of memory
- Index(es):
Relevant Pages
|
