views:

69

answers:

1

I have an ACT! professional for Windows V11.1, with the latest SQL service pack (SP3) and have an apparent memory leak on the server.

After a restart the ACT! SQL instance (SQLSERVR) consumes almost all the available memory on the server, we have added more memory to the server (it is running under Hyper-V) but it continues to consume it all.

I have not been able to connect to the SQL server instance using management studio in order to limit the amount of RAM it is allocated.

Are there any potential solutions for this? or should I continue to restart the services?

A: 

Not a memory leak, but standard behavior.

How to configure SQL Server max memory usage

SQL SERVER 2008 - Memory Leak while storing Millions of records

+ this excellent blog entry

Other than that...

  • x86 or x64?
  • Server RAM?
  • PAE/AWE/3GB switch
  • DB size?
  • (left field) Trace flag 836 (changes 32 bit memory to act like SQL 2000)
gbn
The problem is that I do not have access to the SQL instance as it came prepackaged with ACT. I did find the ACTDIAG tool on their site which will apparently allow this to be done.
Dan

related questions