03-27-2008 02:14 PM
03-27-2008 02:47 PM
03-27-2008 03:08 PM
03-27-2008 03:18 PM
Royel wrote:The issue with ACT! 2005 was a problem with MSSQL failing to fully release memory. There was a workaround incorporated in ACT! 2006 and the version of MSSQL used with ACT! 2007 and later did not have the problem.There was another thread regarding the ACT! 2008 problem and I believe it is some kind of configuration issue.
03-29-2008 01:37 AM
What's up with Act 2008 and sqlservr.exe sucking up memory? All the way to the point that Act freezes up.
When I start up Act, it will use up 135k of memory and then within an hour (I won't even have to be using Act) it will creep up to about 250k. Also sqlservr.exe will start at 71k (when act is finished opening) and will also creep up to anywhere between 100k and 250k (although, it hit 500k the other day to my astonishment). I can minimize Act and the Act memory usage will go down, but only temporarily, and it won't affect sqlserver.
Also when I quit Act, sqlserver won't free up the memory until I restart the computer.
Is there a way to cap the amount of memory Act an sqlservr use?
Why would Act freeze up when I'm not even doing anything with it?
I'm running XP Pro Core 2 Duo 2GHz 2 GB memory.
04-20-2009 11:06 AM
I have found the solution to this problem. Believe it or not, it's Vista. Vista seems to have a much better time handling memory, .Net and sqlserver. I used to have all kinds of problems with Act on XP. Now that I'm on Vista, I couldn't be happier.
Core 2 Duo
7200 rpm SATA drive
and 2 Gig of memory
seem to help too.