S
Steve
Hi,
My firm has a system developed in Microsoft Access 2003 that is deployed as
..MDE's by opening and saving using Microsoft Access 2007. The system is
connected to an SQL Server 2005 Database using ODBC.
The Microsoft Access 2007 system is deployed on a Windows 2008 R2 64 Bit
Application Server and connects to the SQL Server 2005 database on a Database
Server. Multiple users connect to the Microsoft Access 2007 system front end
using Terminal Server.
Our problem is that the MSACCESS.EXE*32's are continuosly growing in size as
the system is used. For example if a user simply opens and closes a form then
the MSACCESS.EXE*32 will continue to increase in memory usage as long as the
user keeps doing this. Memory (Private Working Set) in Task Manager continues
to grow as does Commit Size. We have users where the MSACCESS.EXE*32 is
getting up to 300+ Mb in memory usage.
Would you please assist. What should we start looking at? Is there a Memory
limit that may be set for each instance of the MSACCESS.EXE*32? Is there a
Memory Management facility on the Windows 2008 Server? Is the problem
associated with Jet?
Thanks in advance for any assistance.
NB:- I also posted this in Database Design but General Questions is probably
more appropriate.
Regards,
My firm has a system developed in Microsoft Access 2003 that is deployed as
..MDE's by opening and saving using Microsoft Access 2007. The system is
connected to an SQL Server 2005 Database using ODBC.
The Microsoft Access 2007 system is deployed on a Windows 2008 R2 64 Bit
Application Server and connects to the SQL Server 2005 database on a Database
Server. Multiple users connect to the Microsoft Access 2007 system front end
using Terminal Server.
Our problem is that the MSACCESS.EXE*32's are continuosly growing in size as
the system is used. For example if a user simply opens and closes a form then
the MSACCESS.EXE*32 will continue to increase in memory usage as long as the
user keeps doing this. Memory (Private Working Set) in Task Manager continues
to grow as does Commit Size. We have users where the MSACCESS.EXE*32 is
getting up to 300+ Mb in memory usage.
Would you please assist. What should we start looking at? Is there a Memory
limit that may be set for each instance of the MSACCESS.EXE*32? Is there a
Memory Management facility on the Windows 2008 Server? Is the problem
associated with Jet?
Thanks in advance for any assistance.
NB:- I also posted this in Database Design but General Questions is probably
more appropriate.
Regards,