Bound Control on Access Form Causing High Memory Usage on SQL Server

  • Thread starter Thread starter Ken
  • Start date Start date
K

Ken

I got about 50 Access users every day using the SQL Server
2000 database. At the end of the day, SQL Server always
ran out of the memory. Someone told me this is because of
the bound connection on the Access form causing the memory
leak. Is there a way to fix this problem without changing
my Access form design.
 
Hi,


If that is true, that would more likely cause memory leak in the PC
running Access rather than in the SQL Server. Standard maintenance checks,
in MS SQL Server, like running sp_who, would tell if there are there
"broken" connections, and so on. MS SQL Server has tools allowing to find
who and what is actually running, using resources, on its side. Is this
"someone" is just acting or is this someone IS a knowledgeable person, as
far as MS SQL Server is concerned? Note that Access is supposed to use just
ONE ADO connection for all its objects, by default, with an Access Project
( your code use CurrentProject, and is not opening a new connection of its
own, isn't it? ). I hardly see how a memory leak can occur, in those
circumstances, on the server, since the connection is always maintained
open, as long as the Access application runs (by opposition to be open /
close / open on request). It is highly probable that your "someone"
presumes too much, without proof and without foundation to the "accusation"
made, and present his-her hypothesis as facts left to you to disclose... a
case of poor dba, too frequent within the MS SQL Server environment,
unfortunately... but as the proverb goes: who chose husband chose country.


Hoping it may help,
Vanderghast, Access MVP
 
Back
Top