How large should the pagefile be for a server with 128 GB of RAM? I
have 400 GB of local storage, and the DBs will be on a SAN.

thanks in advance

I usually configure my servers with at least 2 pagefiles - on C:\ to have at
least enough size to generate a dump (4GB in most cases) in case the server
crashes and on another partition. Sizes of pagefile should depend on your
load. A 128GB of RAM should not cause a lot of paging unless there are stray
applications that might be running on the same server and consuming paging
resources. Run a PerfMon trace to determine the usage of your page file and
size it up accordingly. The Microsoft recommendation of 1.5X your RAM is way
too much to consume space for local disks

"JOH" <JOHolloway (AT) gmail (DOT) com> wrote

This is a replacement server, but what it's replacing is an old
machine with barely 100 GB disk and 3 GB RAM. That old machine is
doing ok with a small pagefile of 2 GB.

The new machine has a single partition of local storage with 400 GB,
and the server is attached to a SAN with 1 TB.

I plan to consolidate other servers onto this machine.

I have a 64-bit server with that much ram and my pagefile is 300GB.
It is a lot of space, but apps will always fill up whatever space you give
them. So having enough swapfile is critical.
Don't be afraid to use the space you have. If you don't need that much
pagefile it won't do any harm.
--
http://MidnightDBA.ITBookworm.com

http://www.ITBookworm.com

Blog Author of:
Database Underground -- http://infoworld.com/blogs/sean-mccown
DBA Rant – http://dbarant.blogspot.com




"JOH" wrote:

I assume you have 64bit system installed, prefer avoiding paging as much as
possible...

I suggest enabling Loack pages in memory to avoid database pages getting
swapped to page file...this is to ensure best performance from available
ram...enable paging only if you really have a system which need more than
128gb of ram most of the time....see below...


http://www.tipandtrick.net/2008/enab...aging-to-disk/


"JOH" wrote: