Large Amount of Memory crittical Alert on sqlservr 1

[attrofy]

We are running W2k3 SBS, which includes the SQL Server. We dont use Sql Server, and I have never configured it. However, every day, in my daily logs I am given a critical alert about ALLOCATED MEMORY, and too much memory being used. In checking the logs, I see sqlservr is constantly the memory hog.

Top 5 Processes by Memory Usage
Process Name - ID Memory Usage 

sqlservr - 1096    1,664 MB      
 
store - 3528         338 MB      
 
services - 732        87 MB      
 
Rtvscan - 2908        50 MB      
 
w3wp - 7420           50 MB

However, I can only find two process threads running on the server that have anything to do with SQL. sqlmangr.exe, and I forget the other one at the moment (as I dont currently see it running). Both of these are being used by the Exchange server, so ending them seems to be problematic. We dont get that many emails, and even though we are running an intranet system with the Exchange server, it doesnt get much if any usage at the moment. THese problems go away after a reboot - for a few days - then the same process begins its memory leak again. Is there something else that could be hogging so much memory bandwidth that I am overlooking? We have a pretty limited scope server - at the moment is basically just acting as DC, and hosting mail service for two users. As the problems get straight, we will bring more online. But with 4Gb of memory, having almost a quarter of it dedicated to a service we arent even using just seems to be a configuration problem somewhere. Oh, Sql Server Service Manager is stopped - or more correctly - Not Connected. Any thoughts - thanks in advance for the help.

 

[attrofy]

I want to thank you for all of your help. It will be a few days yet before I can tell if this worked as it seems to have. We had a reboot this weekend due to an extreme overheat in the office. So I spent today fixing a few isuues. It usually takes a few days for the "leak" to develop. I will report back if there are still issues. If not, thanks again for all your help with this.

 

[mrdenny]

No problem. Sounds good. Hopfully it's all fixed.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com