locked
SQLserver.exe memory usage 4GB RRS feed

  • Question

  • Hi

    Is there anyway to cap this memory usage ?

    I believe that the MSSQL$MICROSOFT##SSEE service is causing this .

    I have followed the steps in this blog, however it doesn't appear to affect the memory usage, even after Restarting the Windows Internal database (MICROSOFT##SSEE) service.

    Please advise what I need to do.

    Thanks

    Below is a screen shot of the SQLserver.exe memory usage after restarting the service. It will start to then creep slowly upto 4GB , where is will then remain at this size until the service is restarted

    Thursday, July 26, 2012 9:21 AM

Answers

  • You're trimming the wrong SQL instance by the looks of it. MSSQL$MICROSOFT##SSEE is WSUS, not the monitoring instance.

    Take a look at these instructions - I did exactly the same for the WSUS (MSSQL$MICROSOFT##SSEE) instance on SBS 2011 two days ago and it worked instantly:

    http://msmvps.com/blogs/bradley/archive/2010/11/08/throttling-the-memory-in-sbs-2008.aspx

    You need to use the specific syntax to access the WSUS instance:

    \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

    I also used this syntax to trim the monitoring and sharepoint instances too - replacing the MSSQL$MICROSOFT##SSEE with the correct instance name as listed by tasklist /svc

    • Marked as answer by uklogistics Friday, July 27, 2012 8:37 AM
    Friday, July 27, 2012 8:23 AM

All replies

  • What version of SBS?

    Steve

    Thursday, July 26, 2012 5:17 PM
  • There are usually multiple instances of SQL on SBS (one for WSUS, one for SharePoint, etc) and you will need to find the offending one and trim it. I suggest you start with this blog post:

    http://msmvps.com/blogs/bradley/archive/2010/11/08/throttling-the-memory-in-sbs-2008.aspx


    Thanks Robert Crane [MVP-Office365] www.ciaops.com

    Friday, July 27, 2012 2:46 AM
  • Windows SBS 2008
    Friday, July 27, 2012 7:26 AM
  • Windows SBS 2008
    Friday, July 27, 2012 7:26 AM
  • Hi directorcia - I have tried this already and doesn't work.

    I have followed the steps clearly - twice, and doesn't make a difference. Memory usage at the moment is 7GB! . See screenshot



    Friday, July 27, 2012 7:44 AM
  • You're trimming the wrong SQL instance by the looks of it. MSSQL$MICROSOFT##SSEE is WSUS, not the monitoring instance.

    Take a look at these instructions - I did exactly the same for the WSUS (MSSQL$MICROSOFT##SSEE) instance on SBS 2011 two days ago and it worked instantly:

    http://msmvps.com/blogs/bradley/archive/2010/11/08/throttling-the-memory-in-sbs-2008.aspx

    You need to use the specific syntax to access the WSUS instance:

    \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query 
    I also used this syntax to trim the monitoring and sharepoint instances too - replacing the MSSQL$MICROSOFT##SSEE with the correct instance name as listed by tasklist /svc

    Friday, July 27, 2012 8:22 AM
  • You're trimming the wrong SQL instance by the looks of it. MSSQL$MICROSOFT##SSEE is WSUS, not the monitoring instance.

    Take a look at these instructions - I did exactly the same for the WSUS (MSSQL$MICROSOFT##SSEE) instance on SBS 2011 two days ago and it worked instantly:

    http://msmvps.com/blogs/bradley/archive/2010/11/08/throttling-the-memory-in-sbs-2008.aspx

    You need to use the specific syntax to access the WSUS instance:

    \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

    I also used this syntax to trim the monitoring and sharepoint instances too - replacing the MSSQL$MICROSOFT##SSEE with the correct instance name as listed by tasklist /svc

    • Marked as answer by uklogistics Friday, July 27, 2012 8:37 AM
    Friday, July 27, 2012 8:23 AM
  • Yes, you are correct.

    It isn't very clear from the instruction on how to access it.

    I have the maximum server memory to 700MB, and it works, thanks.

    "Now connect to instances using certain syntax:

    Servername\SBSMonitoring is the SQL instance for SBS monitoring.

    The instance for SharePoint is \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query   "

    Should connect to the database like this.

    Friday, July 27, 2012 8:42 AM