Memory Leak on Goldmine Server
Hi,
Of late, Ive been rebooting our SQL 2005 box more often. Previously, I would do a reboot once a month if I was lucky but now, we are rebooting every couple of days.
Ive logged onto the server this morning and fired up the task manager and I can see the Commit Charge growing by 1mb a second. Its currently showing 2545mb of 5223mb. Im summarising when the process gets up to 5223mb this is when the server will require rebooting.
Is this normal behaviour for this process? What can be done to bring the memory leak under control?
Server is running Windows 2003 Server with SP2 applied. From what I can see, there is no SP on the SQL2005 side of things. Have you guys got any advice about applying Service Packs to Goldmine, any problems or steps I need to be aware of ?
Thanks
DW
Of late, Ive been rebooting our SQL 2005 box more often. Previously, I would do a reboot once a month if I was lucky but now, we are rebooting every couple of days.
Ive logged onto the server this morning and fired up the task manager and I can see the Commit Charge growing by 1mb a second. Its currently showing 2545mb of 5223mb. Im summarising when the process gets up to 5223mb this is when the server will require rebooting.
Is this normal behaviour for this process? What can be done to bring the memory leak under control?
Server is running Windows 2003 Server with SP2 applied. From what I can see, there is no SP on the SQL2005 side of things. Have you guys got any advice about applying Service Packs to Goldmine, any problems or steps I need to be aware of ?
Thanks
DW
ASKER
Hi GMG,
I will update the SP, from what I can see, its upto SP4, can I just apply that one or do I have to go SP1, Sp2 etc?
DB is set to Full since we do Log Shipping of the Transaction logs to a 2nd server (although I have killed this process whilst I try and find the source of the problem)
DW
I will update the SP, from what I can see, its upto SP4, can I just apply that one or do I have to go SP1, Sp2 etc?
DB is set to Full since we do Log Shipping of the Transaction logs to a 2nd server (although I have killed this process whilst I try and find the source of the problem)
DW
SP's normally contain all upto that SP
SQL Server is a VERY memory-hungry application. It will consume all memory available to it. Don't worry; this is "normal." Installing service packs will not "solve" this because it's not really a problem. The best thing you can do to improve the performance of your SQL server is... add more memory to the machine!
ASKER
Steven,
The server has 4gb installed already and I would love to take it to 8 or even 16gb but this would require me to upgrade the OS to 64bit unless you are aware of a cunning way I can get round this?
Dave
The server has 4gb installed already and I would love to take it to 8 or even 16gb but this would require me to upgrade the OS to 64bit unless you are aware of a cunning way I can get round this?
Dave
No way around that. You must be on a 64bit OS.
ASKER
If I was to rebuild the os to 64bit would I need a 64bit version of Goldmine?
No such thing.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks guys.
Just install the SP like any other update and reboot/restart the SQL server.
As for the memory leak, this problem has been around for a long time and its not generally a GoldMine issue.
SQL2000 used to be worse but SQL2008 is much better. its normal to see this happen in a heavily used system.
Not much you can do about it really. Is your GoldMine Databases set to "Simple" or "Full" recovery?