Re: SBS 2003 SP2 Memory

MY PF is up to 4.75GB and free Physical memory is at 1.8GB. I understand
about the SQL instances and watching their individual need over time. I moved
one today to another drive set and boosted performance on that database. The
counter you indicated is jumping to 5 very few seconds. It's spiked up here
and there but seems to keep fairly steady under 10. Any more suggestions to
keep this at zero or close to it?

"Al Williams" wrote:

Don't forget it takes a day or more for RAM usage to stabilize after a
reboot. STORE in paritcular will grab memory as time goes on (no need to
have free RAM in a server). The counter I indicated basically shows how
much I/O is being done to the pagefile. It should stay at zero for the most
part if your server rarely uses the pagefile (which is the goal).

Rather than setting all SQL's to the same RAM you'd be better off tuning
each of them based on usage so watch their RAM usage for a week or more and
then adjust accordingly. Not sure if restricting the CPU was needed - you
have plenty of CPU power.

--
Allan Williams

--
Allan Williams




R. Riddle wrote:
I can use perfmon however I normally do not know what should be my
baseline. Is there a good reference site or document that lists the
major counters and good baseline specs? I followed the suggestion of
Leythos above and the results were not as good as I had hoped. I set
the page file to 4096 min/max and set all SQL instances to use only
256MB and every odd processor. After multiple reboots last night I'm
currently at 4.45GB PF with Physical Memory Available of 2.25GB. I
wont know if anything has helped until the problem returns but I'll
run some perfmon counters to see if I can determine what the existing
bottlenecks are. Sharepoint and Microsoft##SSEE have been removed as
they were not being used.

"Al Williams" wrote:

Use perfmon to look at your paging file IO to see if it is a
bottleneck. This counter is one of the better indicators of actual
pagefile usage bootlenecks according to what I've read:

Memory, Pages Output/Sec - this shows how many virtual memory pages
were written to the pagefile to free RAM page frames for other
purposes each second.

See:
http://support.microsoft.com/kb/555223

Generally with servers you should have enough RAM that you shouldn't
be using your pagefile at all. As others have said some SQL tuning
may be in order but you have an awful lot on that one box. You can
also use Perfmon to see if you have other bottlenecks like a slow
I/O subsystem.

Given the strange login behaviour it sounds like you have other
issues though. Best to tackle each separately. Anything in the
event logs when you login?


--
Allan Williams




R. Riddle wrote:
I have a HP Proliant ML350 G5 running 2 quad core processors @
2333MHz and 4GB of ram. This machine has 2 150GB SATA hard drives
mirrored for the OS and 4x512GB hard drives in RAID 5 for data,etc.
Its the only server in my network and I'm running the following:

Exchange 2003
Blackberry Server (sql database)
Symantec Backup Exec (sql database)
MISys SBM ERP (sql database)
QuickBooks Pro 2007 (Quickbooks database manager)
SonicWall ViewPoint 5.0 (MYsql database)
Mcafee Groupshield

These are the main applications. The problem I have is in the Task
Manager I'm showing the PF usage to hover around 5.0GB and there are
times where the server will go unresponsive for anywhere from 30sec
to minutes (usually no more than 5min). I'll do a reboot and all
will run well for a few days then it starts again. When it does this
nothing is different that I can see. Processor usage is always low
and the PF usage is always between 4.7GB and 5GB. When I try to log
in to the server it can take up to 30 minutes and normally hangs on
a black screen (at the console) or it will sometimes show me
"applying user settings" via remote desktop.

I've had no luck whatsover determining the problem thus far so I'm
wondering if I am set up to use my 4GB of memory correctly. Here is
my boot.ini switches:

/noexecute=optout /fastdetect /pae

I understand I may be looking at multiple issues here so anyone that
has ideas please chime in.



.

Relevant Pages

  • Re: Performance problems -- need guidance on scaling
    ... Thanks for the update on the FT Catalog corruption, ... will use, up to a max of 512Mb, if this memory is available. ... a server with 512 MB of RAM and a resource_usage value of 5 ... the data, you could, detach your SQL 2000 mdf & ldf files ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Memory Issues
    ... Exchange and SQL Server. ... you identified memory problems and large amounts of paging. ...
    (microsoft.public.sqlserver.setup)
  • Re: Memory issues with 64-bit SQL Server 2005 on 64-bit Win 2003 Clust
    ... The Paging File usage is due to how the large memory allocation APIs work. ... Swap files for SQL do not need to be more than about 2-4 GB regardless of physical memory on the box. ... If you use Performance Monitor to track actual paging activity, you will see very little on a properly tuned SQL Server. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Memory issues with 64-bit SQL Server 2005 on 64-bit Win 2003 C
    ... Manager nusance has been around, and yet they somehow could never find time ... counter Total Server Mmeory shows 18GB. ... due to how the large memory allocation APIs work. ... Swap files for SQL do not need to be more than about 2-4 GB ...
    (microsoft.public.sqlserver.clustering)
  • Re: Allocating more memory to sql server
    ... Are you sure you have Windows 2000 Advanced Server and not just Server? ... SQL Server. ... memory used by SQL Server that will give a better idea of the actual usage. ... You also need to restart SQL Server after enabling AWE for it to take ...
    (microsoft.public.sqlserver.setup)
Loading