Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 SQLSERVR.EXE consumes alot of memory

Author  Topic 

AskSQLTeam
Ask SQLTeam Question

0 Posts

Posted - 2003-02-07 : 09:24:55
tapman writes "Hi there,

My problem is that on my server which has SQL Server 7.0 SP4, on Windows 2000 Terminal Server edition with 512 MB memory, the process SQLSERVR.EXE consumes lots of memory.

I have configured server for dynamically using memory from 0 to 152 MB and yet it takes as much as 215 MB memory.
When I start the sql server service it starts with 7-8 MB RAM and then keeps on capturing more and more RAM which goes as high as 215 MB. It creates problem for other applications.

After some time, e.g. 3 hrs, 6 hrs, 12 or 24 hrs or even 2-3 days, suddenly the memory acquired by sqlservr.exe drops down to 30-40 MB and again it starts the whole cycle of capturing memory.

Please provide me the solution to this problem.

Thanks.
tapman."

jasper_smith
SQL Server MVP & SQLTeam MVY

846 Posts

Posted - 2003-02-07 : 12:35:07
Buy a proper server to put SQL Server on
Seriously the behaviour with regards to memory that you are seeing is SQL Server's normal behaviour. You are not giving it a lot of memory to play with. THe max server memory setting in SQL server applies ONLY to the buffer cache. SQL Server needs more memory for extended stored procedures, executables etc so it is likely to consume more than the setting you specify. If you can't justify a dedicated server foe SQL (despite your problems) then get a lot more memory. Here's a KB article explaining SQL Server's memory usage [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363[/url]


HTH
Jasper Smith
Go to Top of Page

JamesH
Posting Yak Master

149 Posts

Posted - 2003-02-07 : 12:46:34
If I'm understanding you correctly your box is a SQL Server and a Terminal Server.

"When a client runs an application on a Terminal Services-enabled Windows 2000 server, all client application execution, data processing, and data storage occurs on the server. " --MS

Your best bet is to let SQL Server reside on its own server without having to fight other applications for resources.

JamesH.

Go to Top of Page

MichaelP
Jedi Yak

2489 Posts

Posted - 2003-02-07 : 13:01:25
Having both Terminal Services and SQL Server on the same PC is going to require a LOT of RAM. I'd got for 1-2GB's of memory at least if they are on the same PC, 1 GB per server if you separate it out to two different servers.

Michael

<Yoda>Use the Search page you must. Find the answer you will.</Yoda>
Go to Top of Page
   

- Advertisement -