May 4, 2005 at 9:46 am
We have several Sql Servers, but we have one server that
the sqlservr.exe task is using 1.72+ GB of memory and CPU runs about 50
compared to others that are using about 174 MB.
What is the best way to determine why this is so high?
May 4, 2005 at 10:08 am
Unless you specify a hard cap SQL will take memory when it needs it. You could have an application running against the database which is causing large queries to be run, pulling in memory.
Have you checked the running processes within SQL to see if there are any runaway statements?
May 4, 2005 at 10:13 am
Do you have any tools at your disposal, like SpotLight? You can use QA and sp_who2 to find out what may be processing. Or in EM, go to Management->Current Activity->Process Info to see who's executing something. Checking the memory can be done using Profiler. SpotLight can do a lot of what you're looking for though, I use it quite a bit (I'm sure there are other tools out there as well).
Terry
May 4, 2005 at 10:34 am
Thanks for the feedback...being a newbie, can you provide the steps to check for runaway statements. I use task managar to view processes but how to check runaway statements....also how to set a cap?
How do I start/use Profiler?
May 4, 2005 at 12:04 pm
Use QA as mentioned in this post, it will tell you what's running inside SQL.
To set a cap on memory you should probably go through Enterprise Manager, into properties, memory and set the max value.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply