bowlerman25
asked on
sql database server very slow, pages/sec very high
We run 3 virtual servers running windows server 2008 on our hp server that runs xenserver 5.6. All workstations are actually on a workgroup but we run active directory on same vm as sql. Application server on 2nd vm. 3rd vm is the terminal server.
We run one application in that rdp session. We have 2 cisco small business smart switch one 48port and one 50 port with poe. I have reset both configs. We have Avg business 2013 installed and have it on every vm, saying up to date and no infections. We are having random freezing or slowness but all rdp sessions stay connected.
After i have done some performance monitor on our sql server, that seems to be the issue. it has pages/sec as high as 1100. we have about 50 computers rdp into the ts then they open the application that pulls from the sql server.
the picture i took was off hours, i will be taking one during hours. the virtual machine has 40gb of memory and 33gb sql keeps taking from the system. the page file is around 35gb and everyone is complaining about slowness. what can i do to improve this?
counters.gif
We run one application in that rdp session. We have 2 cisco small business smart switch one 48port and one 50 port with poe. I have reset both configs. We have Avg business 2013 installed and have it on every vm, saying up to date and no infections. We are having random freezing or slowness but all rdp sessions stay connected.
After i have done some performance monitor on our sql server, that seems to be the issue. it has pages/sec as high as 1100. we have about 50 computers rdp into the ts then they open the application that pulls from the sql server.
the picture i took was off hours, i will be taking one during hours. the virtual machine has 40gb of memory and 33gb sql keeps taking from the system. the page file is around 35gb and everyone is complaining about slowness. what can i do to improve this?
counters.gif
ASKER
why is "All workstations are actually on a workgroup but we run active directory on same vm as sql.
This is NOT recommended. "
why is this not recommended? i have this setup at a couple places and it works great.
also with all users on the server up 3000pages/sec for memory, page faults as high at 6000-10000 but mostly around 3000 or less. processor interrupts are as high as 12000. are any of these an issue? do i need to post different counters so someone can help?
This is NOT recommended. "
why is this not recommended? i have this setup at a couple places and it works great.
also with all users on the server up 3000pages/sec for memory, page faults as high at 6000-10000 but mostly around 3000 or less. processor interrupts are as high as 12000. are any of these an issue? do i need to post different counters so someone can help?
Read this
SQL has a habit of sucking up lots of memory and when running combined with a dc lots of stuff happends when memory is in shortage. Not sure if you've experience this in terminal servers?
Did you constrain max memory setting btw?
SQL has a habit of sucking up lots of memory and when running combined with a dc lots of stuff happends when memory is in shortage. Not sure if you've experience this in terminal servers?
Did you constrain max memory setting btw?
ASKER
can you tell me where exactly it is to limit the memory?
To improve performance i was thinking about doing this. also we are running sql and AD on same vm. I will make the 2nd vm be a dc then i read i have to uninstall sql then demote the original dc then reinstall sql? is that correct?
To improve performance i was thinking about doing this. also we are running sql and AD on same vm. I will make the 2nd vm be a dc then i read i have to uninstall sql then demote the original dc then reinstall sql? is that correct?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
both answers are good, we did not solve issue yet
In case it's not SQL that grabs the memory you should monitor which process consumes most memory. I have seen sql server doing very little but grabs lots of memory.
SQL Server often grabs as much memory as can and doesn't release it until the server needs it "badly".
This is NOT recommended.