asked on SBS 2008 SQL 2005 & MICROSOFT##SSEE Not Releasing Memory
I am using Backup Exec 2010 R2 on this SBS 2008 server, and it backs up 20Gbs of data. It take about an hour and half or even two hours to do so. I believe the slow down is backing up the System State. I also need to mention, this is clean install of the OS and Backup Exec 2010 only. I have all OS services pack and patches applied, and Backup Exec is all up-to-date too. I noticed the problem is the Windows Internal Database (MICOSOFT##SSEE) sqlservr.exe consumes 4Gbs+ of memory, and does not release the memory unless the Windows Internal Database service is restarted, or the server is rebooted, or if the sqlservr.exe (SQL Server Windows NT -64-bit) process is terminated.
I decided to implement the max amount of memory to 2147Mbs for both the MSSQL$MICROSOFT##SSEE and SBSMonitoring SQL instances as per the following article:
http://msmvps.com/blogs/bradley/archive/2010/11/08/throttling-the-memory-in-sbs-2008.aspx
I have noticed the sqlservr.exe process now remains active witth a max memory allocation of 2.295,396K. I am not sure if this actually the best thing to do. Maybe what should be done is simply leave the default memory settings alone, and simply restart both the SBSMONITORING and MSSQL$MICROSOFT##SSEE services every morning at 5AM. A simply batch file with the following commands should do, but my concern is I do this will it possibly cause some sort of corruption or problems down the line.
net stop mssql$sbsmonitoring
net start mssql$sbsmonitoring
net stop mssql$microsoft##ssee
net start mssql$microsoft##ssee
This server installation was done using the defaults. I am not sure if I should leave the max memory settings as is, or restore the default setting back, or simply restart the services as described above, or even simply leave everything as is. I just want to new server to run smoothly, and have all the programs get along and place nice with each other.
I decided to implement the max amount of memory to 2147Mbs for both the MSSQL$MICROSOFT##SSEE and SBSMonitoring SQL instances as per the following article:
http://msmvps.com/blogs/bradley/archive/2010/11/08/throttling-the-memory-in-sbs-2008.aspx
I have noticed the sqlservr.exe process now remains active witth a max memory allocation of 2.295,396K. I am not sure if this actually the best thing to do. Maybe what should be done is simply leave the default memory settings alone, and simply restart both the SBSMONITORING and MSSQL$MICROSOFT##SSEE services every morning at 5AM. A simply batch file with the following commands should do, but my concern is I do this will it possibly cause some sort of corruption or problems down the line.
net stop mssql$sbsmonitoring
net start mssql$sbsmonitoring
net stop mssql$microsoft##ssee
net start mssql$microsoft##ssee
This server installation was done using the defaults. I am not sure if I should leave the max memory settings as is, or restore the default setting back, or simply restart the services as described above, or even simply leave everything as is. I just want to new server to run smoothly, and have all the programs get along and place nice with each other.
SBSMicrosoft SQL Server 2005
Last Comment
cmp119
It's good to leave the sql as per default settings unless you need them to configure to use a range.
SQL behaves in it's own way like it will take memory what ever it requires and releases the memory if it doesn't require. Please check the dependency of apps running on the sql and check the memory utilization at a peak state.
As you mentioned Sql is not releasing memory... It will be not like the way sql plays, might be some sessions are running on the background in sleeping mode...have you checked..!
so keep sql as per default settings and lets keep an eye on the processes running on the background so that we can figure out which processess are making the sql to utilize more memory, according to that we can necessary action to get this issue resolve......
--Venkat
SQL behaves in it's own way like it will take memory what ever it requires and releases the memory if it doesn't require. Please check the dependency of apps running on the sql and check the memory utilization at a peak state.
As you mentioned Sql is not releasing memory... It will be not like the way sql plays, might be some sessions are running on the background in sleeping mode...have you checked..!
so keep sql as per default settings and lets keep an eye on the processes running on the background so that we can figure out which processess are making the sql to utilize more memory, according to that we can necessary action to get this issue resolve......
--Venkat
ASKER
I've requested that this question be deleted for the following reason:
I found my own solution.
I found my own solution.
>>I found my own solution.<<
Please share it with the EE Community so that we can all learn.
Please share it with the EE Community so that we can all learn.
The author was provided good feedback, unfortunately they chose not to followup or provide their own solution.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
you want the dbms to utilise all the memory you allocate to it ... and it will do so...
even to the extent of doing extra work in the initial phases aftyer start up to ensure that its buffer pools are
full...
it is up to you DBA/ Server Administrator to consider what the optimal balance is for your system , partiiculaly if you have
multiple instances of a database server running or are sharing the server between the databases and other applications
as to what degree of ram and/or processors you allocate to each service...