HP ProLiant DL980 G7 Server - Manual (Page 33)

Minimum Server Memory (in MB)
Use the Minimum 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.
CheckPoint
The CheckPoint 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.
Lock Pages in Memory
Lock Pages in Memory is a setting for use on 64-bit operating systems. When this setting is enabled,
Windows retains the SQL Server process working set (the committed, buffer pool memory) in
physical memory until the application in use frees the memory or exits. The Windows operating
system prevents the SQL Server from paging (swapping) the data to virtual memory on disk or from
trimming the data. However, the Windows operating system can still page out the nonbuffer pool
memory within the SQL Server process. Locking pages in memory can improve server performance
and responsiveness when paging memory to disk occurs. By default, this setting is turned off on
64-bit systems.
MaxWorkerThreads
Use this option to configure the number of worker threads available to Microsoft SQL Server
processes. Thread pooling helps optimize performance when large numbers of clients are connected
to the server. Usually, a separate operating system thread is created for each query request.
However, with hundreds of connections to the server, using one thread per query request can
consume large amounts of system resources. The MaxWorkerThreads option enables SQL Server
to create a pool of worker threads to service a larger number of query request, which improves
performance.
Xp_CmdShell
HP ESO displays this parameter for the SAP Database Engine only. Some SAP transactions such
as those made by the database monitor need to execute the stored procedure xp_cmdshell.
This fails unless you have set the SAP Database Engine Xp_CmdShell configuration option to 1.
To execute the stored procedure, select On (this is equivalent to setting it to 1) at the drop down
box, as shown in
Figure 31 (page 34) .
Optimizations pages 33