Lightweight pooling, Priority boost, Min server memory (in mb) – HP ProLiant DL980 G7 Server User Manual

Page 17: Maximum server memory (in mb), Check point, Database

Advertising
background image

Lightweight Pooling

Use the Lightweight Pooling option to reduce system overhead associated with the excessive context
switching sometimes seen in symmetric multiprocessing (SMP) environments. When excessive
context switching is present, lightweight pooling can provide better throughput by performing the
context switching inline, thus helping to reduce user/kernel ring transitions.

Priority Boost

Use the Priority Boost option to specify whether Microsoft SQL Server should run at a higher
Microsoft Windows 2000, Windows Server 2003, Windows Server 2008, or Windows Server
2008 R2 scheduling priority than other processes on the same system. If you set this option to 1,
SQL Server runs at a priority base of 13 in the Windows 2000, Windows Server 2003, Windows
Server 2008, or Windows Server 2008 R2 scheduler. The default is 0, which is a priority base
of 7.

Min Server Memory (in MB)

Use the Min Server Memory option to specify whether SQL Server should start with at least the
minimum amount of allocated memory and not release memory below this value. Set this value
based on the size and activity of your SQL Server instance. Always set the option to a reasonable
value to ensure the operating system does not request too much memory from SQL Server and
inhibit Windows performance.

Maximum Server Memory (in MB)

The Maximum Server Memory option specifies the maximum amount of memory SQL Server can
allocate when it starts and while it runs. Set this option to a specific value if you know there are
multiple applications running at the same time as SQL Server and you want to guarantee these
applications have sufficient memory to run. If these other applications, such as Web or e-mail
servers, request memory only as needed, then do not set the option because SQL Server will release
memory to them as needed. However, applications often use whatever memory is available when
they start and do not request more if needed. If an application that behaves in this manner runs
on the same system at the same time as SQL Server, set the option to a value that guarantees the
memory required by the application is not allocated by SQL Server.

Check Point

The Check Point option writes all dirty pages for the current database to disk. Dirty pages are data
pages that have been entered into the buffer cache and modified, but not yet written to disk. Check
points save time during a later recovery by creating a point at which all dirty pages are guaranteed
to have been written to disk.

Database

The Database page contains parameters related to database files in each SQL Server instance.

Optimizations Pages

17

Advertising