Re: memory issue using ADO to query Excel

From: arno (schoblochr_at_azoppoth.at)
Date: 06/18/04 

Date: Fri, 18 Jun 2004 19:03:19 +0200

Hi Jamie,

> > make sure that you set _all_ objects to nothing when you finished your
code!
> > Esp. the connection string.
>
> Any particular reason for this advice?

run queries eg. in a loop and never cleanup. each query will take longer and
longer and the memory usage of excel (task manager) will grow and grow.

> impeccably.
sorry, I do not know this word. anyway: do not clean up = wait.

arno

Relevant Pages

  • Re: Query optimizing
    ... so the loop is for every username, we follow the following set of 3 ... considering this as a sample of the seven queries i am passing in the ... how do i break this down to simple single query, ...
    (microsoft.public.sqlserver.clients)
  • long running queries quit - audit logout
    ... I have a web based application that launches sql queries using ADO from ... is that the first query runs, sometimes for up to 90 minutes, seems to ... query would start and they would all run until the loop is complete. ...
    (microsoft.public.sqlserver.server)
  • long running queries quit - audit logout
    ... I have a web based application that launches sql queries using ADO from ... is that the first query runs, sometimes for up to 90 minutes, seems to ... query would start and they would all run until the loop is complete. ...
    (microsoft.public.sqlserver.programming)
  • RE: In DotNet Component using Tranaction state ReadUncommited for long
    ... Looking at the query I have following suggestion which could increase the ... Execute all your queries outside of for..next loop. ... In your query use joins instead of sub-query. ...
    (microsoft.public.dotnet.framework.component_services)
  • Looping through queries
    ... I have a series of queries that I need to loop over. ... INNER JOIN UserGroups ... I then need to loop over the last query which is a stored proc, ...
    (microsoft.public.sqlserver.programming)