Re: sqlservr.exe taking 90% of memory
- From: "Brian Cryer" <brianc@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 16 Nov 2007 12:09:38 -0000
"Bob" <bob4sold@xxxxxxxxxxxxxxxx> wrote in message
news:u95b2O%23JIHA.4712@xxxxxxxxxxxxxxxxxxxxxxx
I have pretty much nailed this down that every hour at 45 minutes pass the
hour the whole network slows to a crawl. Outlook pops up and says its
trying to retrieve from exchange, can't access a file, everything just
hangs for a minute to three minutes. I have gone to the server and opened
task manager (that takes over a minute when this is going on) and it shows
sqlservr.exe using 90 to 93 % of the CPW.
By CPW I assume you mean CPU? So the real question is why is it using so
much CPU? It might be worth asking this on an sql server specific newsgroup.
It would be interesting to have SQL Server Manager running and take a look
at what connections are open to what databases and which are active when the
slow down happens. That might give you a clue.
Also, are any of your databases set to "auto shrink"? I think that hits the
database server every 30 minutes, which if you are having a slowdown at 45
minutes past the hour would imply another spike at 15 minutes past the hour.
SBS 2003 Standard, two nics, I GIG memory. Could it be because I'm
running real low on drive C space? Have about 670 megs left. I've moved
exchange stores to a different partition along with the swap file. I
found a thread with some other suggestions for moving other items on C and
I'll do it this weekend.
I run an SBS server with 1GB of RAM and it performs quite happily, but I
don't run a database on it and it only supports a couple of users for
Exchange and file sharing. It seems to be a standard recommendation to have
at least 2GB, and given that both Exchange and SQL Server can be quite
hungry for memory it would be wise to look into upgrading to 2 or 4GB RAM.
Claus' post is good (on both his points) - if your disk is heavily
fragmented (which it might be given how little free space you have left)
then that could have a serious effect on performance. I have seen a sql
server database on a go slow which was caused only by excessive disk
fragementation - rare, in the main I think defragmentation is over rated,
but it can have a dramatic effect on performance. If you run the windows
defrag and in the report you can see that one or more of the databases files
are heavily fragmented then (when its convenient with your users) shutdown
the database and do a defrag. It would be as well also to migrate to a
larger C drive.
If when you resolve the problem you find it was something else completely
then do please post back for the benefit of the rest of us.
--
Brian Cryer
www.cryer.co.uk/brian
.
- Follow-Ups:
- Re: sqlservr.exe taking 90% of memory
- From: Bob
- Re: sqlservr.exe taking 90% of memory
- References:
- sqlservr.exe taking 90% of memory
- From: Bob
- sqlservr.exe taking 90% of memory
- Prev by Date: SQL 2000 on SBS 2003
- Next by Date: Re: Pop mail to mail enabled Pub folder
- Previous by thread: Re: sqlservr.exe taking 90% of memory
- Next by thread: Re: sqlservr.exe taking 90% of memory
- Index(es):
Relevant Pages
|
