Allocated Memory Alert

7945 pts.
Tags:
SBS 2003
SBS 2003 R2
SBS Allocated Memory Alert
SBS Installation
SBS Performance
SQL Server
Our clients newly installed SBS 2003 R2 is sending out Allocated Memory Alerts. My co-worker says this is common for SBS installations, something to do with SQL Server. He figures we should maybe shut down the SQL service, as it is not in use at this company. I have certainly seen this crop up on new installations, but have never seen the "fix" - and am wondering if it is just a matter of adding or modifying a threshold? I would like to correct this myself if possible, just could use some input from the experts (since we have lost our server guru). Many thanks for any advice.

Answer Wiki

Thanks. We'll let you know when a new response is added.

If SQL Server isn’t being used by anything disable it. Like all other services you should only be running the ones that you need otherwise you are wasting system resources and getting no benefit.

Discuss This Question: 6  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • AndreaF
    I added a threshold as per the recommendations in the Administrator's Companion Book (gotta love those) and had a look into the possibility of disabling the SQL Server - but I don't believe it was ever enabled to begin with. When I run Sqlmangr.exe, I have blank fields for both server and services. If there is anywhere else I should check I would....but must confess that this is all a strange and wondrous new experience for me (sounds better than saying I am flying blind). Many thanks Mrdenny!
    7,945 pointsBadges:
    report
  • Denny Cherry
    Look in the Services Control pannel and see if anything is listed under SQL Server or MSSQL.
    66,010 pointsBadges:
    report
  • AndreaF
    I did find both SharePoint and SBS Monitoring listed in the services - stopped the SharePoint, left the monitoring on. I was still getting SQL errors (a flood of them, once I stopped the SharePoint services) so I also stopped the SBS Monitoring (thinking that perhaps it was SQL monitoring in particular). That now leaves me without server reports...so that will need to be re-enabled. I'm wondering if I need to remove the Desktop Engine for SharePoint from the programs.....or if this will have any drawbacks?
    7,945 pointsBadges:
    report
  • Dwiebesick
    High memory usage is usually caused by the SBSMonitoring and Exchange store. By restarting the MSSQL$SBSMonitoring service you will notice that the memory usage drops considerably. There are many good SBS specific sites that you should review. SBS Nation or SBS Memory I have tried changing the monitoring threshold on the monitoring and just gave up. I now set my SBS servers to 70 MB for SBSMonitoring using the Microsoft SQL Server Management Studio Express. Of course, if you are a command line guy, then you can do that with osql command line utility. Let us know if you have additional questions.
    2,235 pointsBadges:
    report
  • Denny Cherry
    You should always limit the amount of memory that SQL Server uses as in its default config it will take all the memory that the server has available.
    66,010 pointsBadges:
    report
  • AndreaF
    That same old alert is once again back with us, and although we do have a new server guru...I am trying to learn as much as I can for myself. I am allowed a certain amount of access for basic maintenance - but the first time I mess up anything, that will probably be the end of that, so I try to be very careful when working with something new! I restarted the MSSQL$SBSMonitoring service as recommended, and looked into setting the Page File to use a System Managed Size - but that wanted a restart (not an option at the moment). I also tried to see how I might go about trying Mr Denny's suggestion (You should always limit the amount of memory that SQL Server uses as in its default config it will take all the memory that the server has available.) but could find nothing in my Administrator's Companion that would help me out with the "how to" end of that - or even suggested parameters that I might look for. Any thoughts, suggestions, input always welcome and appreciated!
    7,945 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following