Memory Problems Windows server 2008/sql server 2008
Dear All.
We have the ssas cube server was setup; the server has been very sluggish. Under the Task Manager for the server the physical memory has been at about 99% for most of the time. On a few occasions it got so slow that we resorted to restarting the machine. This seemed to get things faster but when I opened up the task manager again, I noticed that the RAM taken up started at about 4GBs and steadily climbed back up to the 32GBs that are in the machine. When I looked at the processes it seems that sqlservr.exe is taking up about 22GBs, and when I matched up the PID with the instance I noticed it was the process that was servicing the localserver instance of SQL server.
I restarted the sqlservr.exe process and the physical memory went from 99% to about 36%, it stayed there for some time but eventually started climbing up again, and currently it is at 88%.
The above problem I am not able to detect and any reccomendations highly appreciated.
Thanks.
We have the ssas cube server was setup; the server has been very sluggish. Under the Task Manager for the server the physical memory has been at about 99% for most of the time. On a few occasions it got so slow that we resorted to restarting the machine. This seemed to get things faster but when I opened up the task manager again, I noticed that the RAM taken up started at about 4GBs and steadily climbed back up to the 32GBs that are in the machine. When I looked at the processes it seems that sqlservr.exe is taking up about 22GBs, and when I matched up the PID with the instance I noticed it was the process that was servicing the localserver instance of SQL server.
I restarted the sqlservr.exe process and the physical memory went from 99% to about 36%, it stayed there for some time but eventually started climbing up again, and currently it is at 88%.
The above problem I am not able to detect and any reccomendations highly appreciated.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SIM50
In SQL server options, you can specify how much memory to use.
ASKER
Dear SIM50,
Can you elaborate on this statement"In SQL server options, you can specify how much memory to use."
and let me know how to do this.
Thanks
Can you elaborate on this statement"In SQL server options, you can specify how much memory to use."
and let me know how to do this.
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I did some research and i got the results from a query which Calculates average stalls per read, per write, and per total input/output for each database file.
Please see the attached file and recommend me appropriately.
Copy-of-VBS-SQLServerStalls.xlsx
Copy-of-VBS-SQLServerWaits.xlsx
Please see the attached file and recommend me appropriately.
Copy-of-VBS-SQLServerStalls.xlsx
Copy-of-VBS-SQLServerWaits.xlsx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hmmm...
in SQL 2008 there are some memory management issues which do need to be managed.
there are other factors such as IO than can appear to be a memory (or CPU) problem which does require further analysis.
SQL server efficiency is based on a number of things such as indexing.
I would recommend a split :
http:#33736493 50 points
http:#33739464 75 points
http:#33740992 75 points
http:#33743899 75 points as accepted
http:#33744703 50 points
http:#33754061 75 points
in SQL 2008 there are some memory management issues which do need to be managed.
there are other factors such as IO than can appear to be a memory (or CPU) problem which does require further analysis.
SQL server efficiency is based on a number of things such as indexing.
I would recommend a split :
http:#33736493 50 points
http:#33739464 75 points
http:#33740992 75 points
http:#33743899 75 points as accepted
http:#33744703 50 points
http:#33754061 75 points
Starting the automated closure procedure to implement the recommendations from the participating Expert(s).
- thermoduric -
EE Community Support Moderator
https://www.experts-exchange.com/questions/26756950/21-Jan-11-22-Automated-Request-for-Review-Objection-to-Delete-Q-26492070.html
- thermoduric -
EE Community Support Moderator
https://www.experts-exchange.com/questions/26756950/21-Jan-11-22-Automated-Request-for-Review-Objection-to-Delete-Q-26492070.html