March 15, 2004 at 11:58 am
SQL server will use as much as memory it was asigned, and will release some of the memory when OS calls. How to find out whether it is memory leak Since SQL server does not release memory?
March 15, 2004 at 12:28 pm
For us newbies, please describe the problem you are encountering.
TIA
GaryA
March 15, 2004 at 7:47 pm
We are all interested in assisting you in your issue but we gotta ask the simple stuff first..<Frank K.don't go Fistansie on me please>
Carpe Nox Noctum!
Jbabington
Jbabington@hotmail.com
March 16, 2004 at 6:11 am
We had major memory leak problems with SQL 7, but they magically went away when we upgraded to SQL 2K.
Dana
Dana
Connecticut, USA
Dana
March 16, 2004 at 9:14 am
To be hornest with you, I do not have the performance degradation now, just curious, if the server performance is very bad, how to find out if it is caused by memory leak, what is the metrics. We have 2G RAM, 2 processors with SQL 2k standard edition, the server memory has been set dynamiclly to be managed.
March 16, 2004 at 10:06 am
I've had instances where memory really never went back to the O/S even with it Dynamically configured. I had a monitoring tool in place showing the memory utilized but when no activity for quite awhile the memory utilization never really went back down. (or at least enough to consider it the way MS says!) This w/various SP's and SLQ versions.
March 18, 2004 at 3:00 am
SQL Server is monster in dealing with Memory .. it is recommeded not to use any other programs with SQL Server.
or you must assign a Fixed Memmory
I hope this help u
Alamir Mohamed
Alamir_mohamed@yahoo.com
March 18, 2004 at 6:11 am
I aggree w/Alamir!!
March 22, 2004 at 9:36 am
dbcc memorystatus will give you some clue. Pay special attention to the Dynamic memory manager section. I did have memory leak problem on SQL2K 2 years ago which was due to using OA_ object.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply