Trace flag 8048, Trace flag 834, Trace flag 8048 trace flag 834 – HP ProLiant DL980 G7 Server User Manual

Page 58: Viewing and controlling sql

Advertising
background image

NOTE:

The Process GroupAffinity parameter is not supported with Analysis Services 2008 and

2008 R2 instances; therefore, Analysis Services 2008 and 2008 R2 instances are not displayed
with Process GroupAffinity information.

SQL Startup Option page: Viewing and controlling SQL Server startup options

During SQL Server installation, a set of default startup options is written to the registry . Trace flags
are one form of these startup options. Use trace flags to temporarily set specific server characteristics,
or to switch particular SQL Server behaviors on or off. Trace flags can be used for a variety of
purposes. Many of them, if set appropriately for your environment and workload, can enhance
performance of the SQL Server.

Figure 47 (page 58)

shows an example of the SQL Startup Option

page. The subsections that follow describe the trace flag startup options.

Figure 47 SQL Startup Option page

The SQL Startup Option page lists the status of trace flags available for each particular SQL instance.

Trace flags are very sensitive to the SQL Server edition and versions, and to workload types (SAP,
Data Warehouse, Database Engine). The SQL Startup Option page displays only those trace flags
(and their status) supported by the SQL instance. The page displays a description of each supported
trace flag.

To change the status of an individual trace flag, select a new value from the drop down box and
click SET.

CAUTION:

Each trace flag covers a very specific field and requires certain conditions to work.

Caution should be used when turning a trace flag on or off.

Trace flag 8048

Enable trace flag 8048 (TF-8048) to use memory allocation at the CPU level to reduce costs when
you have too many CPUs per NUMA node. HP ESO recommends and displays this flag for non-SAP
instances only, with systems having at least eight CPUs per NUMA node.

Trace flag 834

When combined with the Lock Page option described previously, this flag forces the SQL Server
to use 2MB pages for the buffer cache instead of the default 4KB pages. This reduces the Translation
Look aside Buffer (TLB) size and contention, and simplifies memory management by reducing the
number of pages to be tracked and manipulated. This flag is recommended particularly on systems

58

Using HP ESO

Advertising