January 14, 2014 at 11:02 am
I have been asked from users about SQLSERVR.EXE. What is SQLSERVR.EXE?
Someone emailed me about "why SQLSERVR.EXE process is limited to about 128MB of RAM and it should be allowed to use at least ½ of the memory on the box."
I am still trying to find the answer since I have no idea what the answer is. Can't find any decent topic which can tell me more about this process. I have 8GB on the box and max memory on sql server is set to 5GB. I don't know if its relevant to this process or not, but just trying to put as much information as I can. Any detail or link which can tell me a little bit about this will be highly appreciated.
"He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]
January 14, 2014 at 12:00 pm
New Born DBA (1/14/2014)
I have been asked from users about SQLSERVR.EXE. What is SQLSERVR.EXE?Someone emailed me about "why SQLSERVR.EXE process is limited to about 128MB of RAM and it should be allowed to use at least ½ of the memory on the box."
I am still trying to find the answer since I have no idea what the answer is. Can't find any decent topic which can tell me more about this process. I have 8GB on the box and max memory on sql server is set to 5GB. I don't know if its relevant to this process or not, but just trying to put as much information as I can. Any detail or link which can tell me a little bit about this will be highly appreciated.
Assuming it's a production server,how are you checking memory usage? maybe you are off by a calculation or other factor.
Is the database on it extremely tiny, or a little-used development server? was it stopped and started recently? While SQL may have been given an upper limit, if the server's not queried, it's not going to stuff data into RAM in the hopes that later connections might need the same data.
for example, my developer machine has sql2012 and 2008R2 installed; i hardly ever query them, and either one is running about 27 meg of ram in use right now.
however, as soon as i query a big table in one of the instances, my memory usage goes up, but it's still less than the 16 gig total available on the machine.
if you can fill in more details, we can offer more advice.
Lowell
January 14, 2014 at 12:23 pm
Thanks for the reply, but I don't know nothing about this server. Somebody was having some issues and my manager emailed me to look for the problem. So today was the first time I actually logged into the system. While I was logged in, a user emailed me and asked me about the sqlservr.exe which I think I should know as a DBA but I don't.
It is a production server. I usually use Task manager to see the memory or cpu to find out which processes is taking memory or CPU and I am sure there are other ways to find out but I just became a DBA and this is all I know for now.
But long story short, All I want to find out if this process is useful. If so, how useful?
"He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]
January 14, 2014 at 12:29 pm
sqlserver.exe is the name of the executable that is running under the SQL service; it is the absolute core and is critical to SQL server...heck it IS sql server.
if you watch that process in Windows Task manager, you are getting a good view of the memory consumption that is part of the pool for SQL, as far as I know.
Lowell
January 14, 2014 at 12:32 pm
Thanks,
"He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]
January 14, 2014 at 3:28 pm
Task Manager does a really poor job of displaying memory usage - especially for SQL Server. To view memory usage for SQL Server it is better to use perfmon and select Target Memory and Total Memory.
To find out how much memory SQL Server is allowed to use, you can open SSMS and connect Object Explorer to that instance. Right-click on the server name and go to properties - check the memory configuration page.
Max Memory is how much memory SQL Server can use.
Min Memory is the minimum amount SQL Server can have. This is a bit different from what you would think - it is not how much memory SQL Server allocates at start up. It is actually a minimum value for what SQL Server will give back when asked. In other words, if SQL Server is configured with min memory of 4GB and max memory of 8GB - it will use up to 8GB - and will only return memory to the OS down to 4GB (if requested by the OS - and SQL Server can release the memory).
The values in the dialog box are in MB and I expect the values will be the default value (2,147,483,647 which is the largest integer value). If so, then you may be running into an issue with SQL Server starving the OS and that could cause performance issues.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
January 15, 2014 at 6:38 am
Thank you so much for replying. It did clear so many things I had in mind about min and max memory.
"He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply