HP Enterprise SQL Optimizer (HP ESO) 3.0
User Guide
Abstract
This document describes how to install and use HP's Enterprise SQL Optimizer (HP ESO) software. HP ESO was created for
system administrators and HP support personnel responsible for installing, configuring, and managing HP ProLiant servers
running Microsoft SQL Server. This document is not a tutorial.
HP Part Number: AM426-9013D
Published: January 2013
Edition: 1.0
© Copyright 2011–2013 Hewlett-Packard Development Company, L.P.
Legal notices
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Microsoft, SQL Server, and Windows are U.S. registered trademarks of Microsoft Corporation.
Publishing history
Manufacturing Part
Number
Supported Operating
Systems
Supported SQL Server
AM426-9013A
Microsoft Windows
Server 2008 R2 x64
Edition with Service Pack
1 (SP1)
Microsoft SQL Server
HP ProLiant DL980 G7
2008 R2 x64 Edition
with Service Pack 2
(SP2) — Enterprise, Data
Center, and Standard
Editions
(HP ESO 1.0)
Microsoft Windows
Server 2008 with
Service Pack 2 (SP2)
AM426-9013A
Supported Products
(Servers)
Publication Date
November 2011
Microsoft SQL Server
2008 x64 Edition with
Service Pack 2 (SP3) —
Enterprise, Data Center,
and Standard Editions
Same as above
Same as above
Same as above
April 2012
Same as above
Same as above, plus
Microsoft SQL Server
2012 — Enterprise,
Business Intelligence,
and Standard Editions
Same as above
June 2012
Same as above
Same as above
Same as above
August 2012
Same as above plus
Microsoft Windows
Server 2012
Same as above
Same as above
January 2013
(HP ESO 1.0)
AM426-9013B
(HP ESO 2.0)
AM426-9013C
(HP ESO 2.1)
AM426-9013D
(HP ESO 3.0)
For the latest version of this document, see the HP Technical Documentation website:
http://hp.com/go/proliant-DL980-docs
Contents
1 Introduction...............................................................................................6
Features..................................................................................................................................6
New features in release 3.0.......................................................................................................7
New features in release 2.0 and 2.1...........................................................................................8
2 Installing HP ESO.......................................................................................9
Software requirements...............................................................................................................9
Installing the software................................................................................................................9
Uninstalling the software..........................................................................................................11
Upgrading the software...........................................................................................................11
Silent installation....................................................................................................................12
3 Using HP ESO..........................................................................................13
Starting HP ESO.....................................................................................................................14
Configuration steps prior to using HP ESO.................................................................................17
Ensure HP ESO user accounts have Microsoft SQL Server administrator privileges.......................17
Ensure HP ESO user accounts have Microsoft Analysis Services administrator privileges...............18
Getting Started.......................................................................................................................20
Quick start: basic session....................................................................................................21
Floating help.....................................................................................................................24
Creating an authenticated Administrator Session (Admin Session).............................................25
SQL Server Login: Setting credentials and logging into SQL Server and Analysis Services
instances..........................................................................................................................25
Modifying the Admin Session timeout value...........................................................................27
Settings pages.......................................................................................................................27
Data Collection page: Collecting data for analysis and optimization recommendations...............27
Optimizations pages...............................................................................................................29
SQL Server page: Viewing and enabling SQL Server and Analysis Services optimization
recommendations..............................................................................................................31
SQL Server database instance parameters........................................................................32
Maximum Degree of Parallelism.................................................................................32
Lightweight Pooling...................................................................................................32
Priority Boost............................................................................................................32
Minimum Server Memory (in MB)...............................................................................33
Maximum Server Memory (in MB)..............................................................................33
CheckPoint..............................................................................................................33
Lock Pages in Memory..............................................................................................33
MaxWorkerThreads..................................................................................................33
Xp_CmdShell...........................................................................................................33
Analysis Services instance parameters..............................................................................34
Flight Recorder.........................................................................................................34
Random File Access..................................................................................................34
LowMemoryLimit.......................................................................................................34
TotalMemoryLimit.....................................................................................................34
CoordinatorQueryBalancingFactor and CoordinatorQueryBoostPriorityLevel.....................34
EnableRolapDistinctCountOnDataSource.....................................................................34
Database page: Viewing and enabling database optimization recommendations.......................35
SQL Server Database Engine properties...........................................................................36
File Growth..............................................................................................................36
Auto Create Statistics................................................................................................36
Auto Update Statistics...............................................................................................36
Auto Update Statistics Async......................................................................................36
Contents
3
Analysis Services properties............................................................................................36
Data Dir..................................................................................................................36
Temp Dir.................................................................................................................36
Log Dir....................................................................................................................36
Backup Dir..............................................................................................................36
Measure Group........................................................................................................37
Partition..................................................................................................................37
Estimated Rows........................................................................................................37
Estimated Size..........................................................................................................37
Proactive Caching....................................................................................................37
ESO database recommendation statements.......................................................................37
Database File on System Drive...................................................................................37
Multiple Database File on a Drive...............................................................................37
Database page: Viewing high availability and disaster recovery configurations.........................37
Availability Group.........................................................................................................37
Mirrored database........................................................................................................38
Clustered SQL Server instance.........................................................................................40
Cluster Network Name.............................................................................................40
Computer Name......................................................................................................40
Status.....................................................................................................................40
Computer Role.........................................................................................................40
CPU page: Viewing and enabling CPU assignment optimization recommendations.....................41
SQL Server affinity........................................................................................................41
Analysis Services Process GroupAffinity............................................................................42
Storage page: Viewing and enabling storage optimization recommendations............................42
Database RAID level......................................................................................................42
User Write Cache Setting...............................................................................................43
User Cache Power Protection..........................................................................................43
Drive free space............................................................................................................43
Volume mount point.......................................................................................................43
Network page: Viewing and enabling network optimization recommendations..........................43
NUMA node affinity......................................................................................................43
Interrupt affinity.............................................................................................................44
Port affinity...................................................................................................................44
Receive-Side Scaling......................................................................................................44
SQL Startup Option page: Viewing and enabling startup options.............................................45
Trace flag 8048............................................................................................................46
Trace flag 834..............................................................................................................46
Trace flag 1117..............................................................................................................46
Trace flag 1118..............................................................................................................46
Trace flag 2371............................................................................................................46
Trace flag 2549............................................................................................................46
Trace flag 2562............................................................................................................47
System page: Viewing and enabling system optimization recommendations...............................47
PCI Controller Information..............................................................................................47
Software Discovery .......................................................................................................48
System software and firmware status................................................................................48
Configuring and initiating Software Discovery............................................................................48
Reports pages........................................................................................................................49
Workload and Performance History......................................................................................49
Save/Rollback SQL Configuration........................................................................................51
Help pages............................................................................................................................54
Online help.......................................................................................................................54
4
Contents
4 Support and other resources......................................................................55
Contacting HP .......................................................................................................................55
Before you contact HP........................................................................................................55
HP contact information.......................................................................................................55
Subscription service............................................................................................................55
New and changed information in this edition.............................................................................55
Related information.................................................................................................................56
Typographic conventions.........................................................................................................56
5 Documentation feedback...........................................................................57
Contents
5
1 Introduction
HP Enterprise SQL Optimizer (HP ESO) is a software tool that greatly simplifies and consolidates
the process of tuning HP ProLiant DL980 G7 servers running Microsoft Windows Server and SQL
Server 2008, SQL Server 2008 R2, or SQL Server 2012. Use HP ESO to:
•
Reduce the time and complexity of configuring and tuning systems running SQL Server
•
Reduce the number of support calls due to misconfigured systems
•
Help users optimize their configuration to ensure top SQL Server performance
•
Improve customer satisfaction
HP ESO achieves these goals by providing optimization tools for the following system components:
•
Server – Includes hardware-related recommendations such as placement of PCI cards and
proper storage drive configurations, and information on the update status of HP software,
drivers, and firmware
•
Operating System – Includes settings for Power Management Options and storage volumes
•
Microsoft SQL Server – Includes settings such as priority boost, light-weight pooling, CPU
affinity, and more
You access these optimization tools by logging into SQL instances. There are two types of SQL
instances:
•
SQL Server Database Engine instances — These service user requests for reading and writing
data in databases for any of three different types of applications:
◦
Online Transaction Processing (OLTP) Database Engine
◦
Data Warehouse (DW) Database Engine
◦
SAP Database Engine
In general, the term “Database Engine” refers to the OLTP Database Engine, unless one of the
other two types of Database Engine is specifically mentioned.
•
Analysis Services instances — These analyze the transactions that occur in the database. It
provides online analytical processing (OLAP) and data mining capabilities.
Features
HP ESO provides the following functionality for configuring and tuning your server and Microsoft
SQL Server:
6
•
Scheduled or manual data collection, for use as reference when optimizing the system and
SQL Server
•
Built in knowledge of the hardware architecture, to properly optimize the server
•
Reports page that provides a graphical display of data collection parameters, for use in
analysis and interpretation, with the ability to export to a file
•
Built-in WBEM-based instrumentation for quick integration with other management tools such
as HP System Insight Manager
•
Capability to roll back to previously saved configurations. Use this feature to save the current
configuration, then retrieve and apply it in the future if necessary
Introduction
New features in release 3.0
HP ESO 3.0 provides the following new features:
•
Windows 2012 support
•
Windows 2012 Server Core support
•
Data Warehouse (DW) / Business Intelligence (BI) identification and support
◦
User interface for entering login credentials for DW and BI instances
◦
Recommendations for optimized settings for the following parameters in DW instances
and databases, based on monitored workload:
◦
◦
◦
•
–
Maximum Degree of Parallelism (MAXDOP)
–
MaxWorkerThreads
–
Startup options (trace flags) T834, T8048, T1117, and T1118
Recommendations for optimized settings for the following parameters in SQL Server
Analysis Services (SSAS) instances, based on monitored workload:
–
ResourceMonitoringEnabled
–
RandomFileAccessMode
–
FlightRecorder
–
EnableROLAPDistinctCountOnDataSource
–
CoordinatorQueryBalancingFactor
–
CordinatorQueryBoostPriorityLevel
–
MemoryLimit (Low/Total)
–
Analysis Services Process GroupAffinity (only for SQL Server 2012 Analysis Services)
Recommendations for optimized storage settings for the following parameters in DW
instances:
–
Database file autogrowth (autogrow)
–
Storage layout of database files
Recommendations for optimized storage settings for the following parameters in SSAS
instances:
–
DataDir, LogDir, and TempDir
–
Custom storage location of databases
–
Partition information such as Proactive Caching, Estimated Rows, Estimated Size
SAP Database Engine identification and support
◦
Recommendations for optimized settings for the following parameters in databases, based
on monitored workload:
–
Maximum Degree of Parallelism (MAXDOP)
–
Checkpoint
–
Xp_CmdShell
New features in release 3.0
7
◦
–
Startup options (trace flags) T1117, T1118, T2371, T2549, and T2562
–
Database auto create/update/async statistics
Recommendations for optimized storage settings for the following parameters:
–
Database file autogrowth (autogrow)
–
Storage layout of database files
•
Improved response times for page loading, saving, and rollback
•
Improved graphical user interface (GUI) on all pages, with most significant changes on:
•
◦
CPU page — CPU affinity settings of all SQL instances are shown side by side for
convenience of comparison and analysis
◦
SQL Startup Option page — Current status and additional details about trace flags in
one single page
Enhanced error handling, including additional detailed error messages presented in GUI and
log file
New features in release 2.0 and 2.1
HP ESO 2.0 additionally provides:
•
Windows 2008 R2 Server core support
•
SQL Server 2012 support
•
Volume Mount Point support (see “Volume mount point” (page 43))
•
New SQL Server Login page that allows users to specify login credentials for SQL Server
instances (see “SQL Server Login: Setting credentials and logging into SQL Server and Analysis
Services instances” (page 25))
•
Session-based usage model to prevent simultaneous access and control of the tool (see “Quick
start: basic session” (page 21))
•
Support for SQL Server startup options (trace flags) settings (see “SQL Startup Option page:
Viewing and enabling startup options” (page 45))
•
Network RSS (Receive Side Scaling) settings recommendations (see “Receive-Side Scaling”
(page 44))
•
New information on HADR (High Availability Disaster Recovery) configured databases and
SQL servers (see “Database page: Viewing high availability and disaster recovery
configurations” (page 37))
HP ESO 2.1 additionally provides a fix for more efficient CPU and memory resources usage.
Previous resources usage caused SQL Server, Database, CPU, and Network optimization pages
to hang for certain storage settings.
8
Introduction
2 Installing HP ESO
Software requirements
The following prerequisite software is required in order for HP ESO to function properly:
•
HP System Management Homepage (HP SMH), Version 6.0 or later
•
Any Internet browser supported by HP SMH (refer to your HP SMH documentation for more
information)
•
Microsoft .NET Framework, Version 3.5 or later
•
Microsoft SQL Server 2012 Shared Management Objects
•
Microsoft System CLR Types for Microsoft SQL Server 2012
•
The following Microsoft SQL Server versions and editions are supported:
◦
Microsoft SQL Server 2012 Enterprise, Business Intelligence, and Standard Editions
◦
Microsoft SQL Server 2008 R2 Datacenter, Enterprise, and Standard Editions
◦
Microsoft SQL Server 2008 Datacenter, Enterprise, and Standard Editions
•
Microsoft SQL Server 2012 Analysis Management Objects
•
HP Insight Management WBEM Providers (highly recommended)
Installing the software
To install HP Enterprise SQL Optimizer, follow these steps:
1. Login as Administrator on the target system.
2. Obtain the HP ESO installation file (file name: cpnnnnnn.exe) and either double-click it, or
right-click and select Open.
3. The first installation window displays, as shown in Figure 1 (page 9). Click Install to continue.
Figure 1 Package Setup window
4.
The second installation window displays, as shown in Figure 2 (page 10). Click Install to
continue. The installation begins, with a progress bar indicating status.
Software requirements
9
Figure 2 Setup window #1
5.
When the installation finishes successfully, as shown by the HP Setup window shown in Figure 3
(page 10), click Close to exit.
Figure 3 Setup window #2
NOTE: The HP ESO application files are installed into the %ProgramFiles%\McPerfOpt
folder, where %ProgramFiles% is typically: C:\Program Files.
If the prerequisite HP Insight Management WBEM Provider software is not installed on the system,
you will see (during HP ESO installation) the warning message shown in Figure 4 (page 11).
10
Installing HP ESO
Figure 4 Installation warning message
Uninstalling the software
To uninstall HP Enterprise SQL Optimizer, follow these steps:
1. Login as Administrator on the target system.
2. Navigate to the Add/Remove panel (or Programs and Features in the Control Panel).
3. Locate “HP Enterprise SQL Optimizer for Windows Server x64 Edition” in the resulting list of
programs. Right-click it and click Uninstall.
4. A confirmation popup displays, asking you to confirm this action. Click Yes to continue.
5. A notification popup displays, confirming that HP ESO was removed. Click OK to close this
popup and complete the process.
Upgrading the software
Upgrading HP ESO from an older version to a newer version is supported. For example, if HP
ESO 1.0.0.0 or 2.0.0.0 is currently installed, you can upgrade to HP ESO 3.0.0.0. The upgrade
process is similar to the new installation process described in “Installing the software” (page 9).
The only exception is the slightly different screen seen when the installation begins, as shown in
Figure 5 (page 12).
Uninstalling the software
11
Figure 5 Upgrade window
Downgrades are not supported. For example, if HP ESO 3.0.0.0 is currently installed, and you
try to install HP ESO 1.0.0.0 or 2.0.0.0, you will see a warning screen as shown in Figure 6
(page 12). If you attempt to continue, you will see an error screen.
Figure 6 Downgrade error window
Silent installation
HP ESO can be installed in silent (non-interactive) mode by adding the /s or /silent switch to
the installer package's executable file, such as cp018233.exe /s when executing. When silent
installation is performed, HP ESO will be installed to completion without any user interaction.
NOTE: During silent installation, the prerequisite Microsoft SQL Management Object package
will be installed automatically if it is not installed in the system. To prevent this from happening,
extract the installer package into a temporary folder by clicking Extract during installation. At the
location of the extracted files, delete SQL_AS_AMO.msi, SharedManagementObjects.msi,
and SQLSysClrTypes.msi, and then execute cpqsetup.exe.
12
Installing HP ESO
3 Using HP ESO
HP ESO allows you to connect to SQL Server and Analysis Services instances to perform a variety
of operations to help with system configuration and tuning to optimize SQL performance. Table 1
(page 13) lists the main tasks you can perform using HP ESO.
Table 1 Tasks to perform
Task to perform...
For more information...
Configuration steps prior to using HP ESO
Launch HP System Management Homepage (SMH) to start HP ESO
“Starting HP ESO” (page 14)
Ensure that user accounts have correct privileges to access SQL Server and Analysis “Configuration steps prior to
Services instances
using HP ESO” (page 17)
Tasks to perform using HP ESO
Getting started: perform a basic session and get help
“Getting Started” (page 20)
Start an individual, authenticated session to enable access to ESO pages and
functionality
“Creating an authenticated
Administrator Session (Admin
Session)” (page 25)
Enter login credentials and authentication type for SQL Server and Analysis Services “SQL Server Login: Setting
instances; log in to SQL instances
credentials and logging into SQL
Server and Analysis Services
instances” (page 25)
Modify Admin Session timeout period
“Modifying the Admin Session
timeout value” (page 27)
Set data collection parameters and initiate data collection and analysis for
optimization recommendations
“Data Collection page: Collecting
data for analysis and
optimization recommendations”
(page 27)
View SQL Server and Analysis Services information and enable optimization
recommendations
“SQL Server page: Viewing and
enabling SQL Server and
Analysis Services optimization
recommendations” (page 31)
View information about database files in each SQL Server and Analysis Services
instance and enable optimization recommendations
“Database page: Viewing and
enabling database optimization
recommendations” (page 35)
View information about high availability and disaster recovery database
configurations
“Database page: Viewing high
availability and disaster recovery
configurations” (page 37)
View information about CPU-thread associations and enable optimization
recommendations
“SQL Server page: Viewing and
enabling SQL Server and
Analysis Services optimization
recommendations” (page 31)
View storage information and enable optimization recommendations
“Storage page: Viewing and
enabling storage optimization
recommendations” (page 42)
View network information and enable optimization recommendations
“Network page: Viewing and
enabling network optimization
recommendations” (page 43)
View SQL startup information and set trace flags to modify SQL Server behavior
“SQL Startup Option page:
Viewing and enabling startup
options” (page 45)
13
Table 1 Tasks to perform (continued)
Task to perform...
For more information...
View system information, including status of add-on PCI controllers, system software, “System page: Viewing and
drivers, and firmware versions; and enable optimization recommendations
enabling system optimization
recommendations” (page 47)
Select the location from where Software Discovery finds system information; run the “Configuring and initiating
Software Discovery process
Software Discovery” (page 48)
Configure and view (or export) data collection reports
“Workload and Performance
History” (page 49)
Save or restore current system configuration information
“Save/Rollback SQL
Configuration” (page 51)
View online help
“Online help” (page 54)
Starting HP ESO
To access and start HP ESO, you must launch the HP System Management Homepage (SMH)
software. SMH is the starting point HP ESO and many other HP server management tools. Follow
these steps to launch SMH and start HP ESO:
1. From the target system Desktop, click Start→All Programs→HP Management Agents→HP
System Management Homepage.
2. When the security certificate warning displays (see Figure 7 (page 14)), click Continue to this
website.
NOTE: To avoid seeing this certificate error message in the future, follow the steps described
in this HP Support webpage:
HP Systems Insight Manager (HP SIM) and System Management Homepage (SMH) - Microsoft
Internet Explorer Does Not Link Website Certificate to all IP or DNS Names Associated with
the Certificate
Also refer to the section “Initializing the software for the first time” in the document, HP System
Management Homepage Installation Guide, found at:
http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c02779495/
c02779495.pdf
Figure 7 Certificate warning window
14
Using HP ESO
3.
The SMH Sign In page displays as shown in Figure 8 (page 15). Enter a valid user name and
password and click Sign In.
Figure 8 SMH Sign in page
Your user name and password must be a valid account in the Administrator group (see Figure 9
(page 16)) configured in the SMH users groups. The Sign In button validates the values in the
User Name and Password fields. If both values are valid, the HP SMH Homepage displays.
The Clear button clears the User Name and Password fields. The Question Mark icon (?)
displays or hides a floating tooltip box containing information about the authentication
mechanism and sign in process.
Starting HP ESO
15
Figure 9 How to configure user name and group in SMH
4.
In the SMH Homepage (see Figure 10 (page 16)), click the HP ESO link in the Enterprise SQL
Optimizer box.
Figure 10 SMH Homepage
5.
16
The Enterprise SQL Optimizer Introduction page displays. An example of this page and
instructions for getting started with HP ESO are included in “Getting Started” (page 20).
Using HP ESO
Configuration steps prior to using HP ESO
Prior to using HP ESO, you might need to perform the following:
•
To ensure that user accounts can access SQL Server instances, set the appropriate server roles
for these accounts, as described in “Ensure HP ESO user accounts have Microsoft SQL Server
administrator privileges” (page 17).
•
To ensure that user accounts can access Analysis Services instances, ensure that each user
account is a member of Analysis Services Server Administrators, as described in “Ensure HP
ESO user accounts have Microsoft Analysis Services administrator privileges” (page 18).
Ensure HP ESO user accounts have Microsoft SQL Server administrator privileges
To use HP ESO to access an SQL Server instance to set parameters and optimize resources based
on the instance’s particular workloads, the user account you intend to use must be assigned the
serveradmin and/or sysadmin SQL Server role. To assign SQL Server roles to an account, follow
these steps:
1. Open the Microsoft SQL Server Management Studio. To open this page from Windows 2008
R2 and earlier, click Start→Programs→Microsoft SQL Server Management Studio. To open
the page on Windows 2012, follow these steps:
In desktop mode
a.
b.
Open the Start Menu charm on the left side of the desktop and change to tile mode.
Click Microsoft SQL Server Management Studio.
In tile mode
Click Microsoft SQL Server Management Studio.
2.
3.
4.
Log in to an SQL Server instance using an account that is able to set permissions for the other
accounts.
Follow these steps, as illustrated in Figure 11 (page 18):
a. In the Object Explorer pane on the left side of the page, select Security→Logins.
b. In the list of accounts under Logins, right click the account that is to be used in HP ESO
and select Properties.
c. From the Login Properties page, select Server Roles.
d. In the list of server roles, check the box of the serveradmin and/or sysadmin role. (The
Public role is checked by default.)
Repeat steps 2 and 3 for all SQL Server instances.
Configuration steps prior to using HP ESO
17
Figure 11 SQL Server Management Studio Login Properties window
Ensure HP ESO user accounts have Microsoft Analysis Services administrator privileges
To use HP ESO to access an Analysis Services instance to set parameters and optimize resources
based on the instance’s particular workloads, the user account you intend to use must be a member
of the Microsoft Analysis Server Administrators group. To ensure that an account is in the
Administrators group, follow these steps:
1. Open the Microsoft SQL Server Management Studio (see the instructions in step 1 of “Ensure
HP ESO user accounts have Microsoft SQL Server administrator privileges” (page 17)).
2. Log in to an SQL Analysis Services instance using an account that is able to set permissions
of other accounts:
a. Select Connect→Analysis Services...
b. In the Connect to Server popup, select the server and click Connect.
3.
18
In the Object Explorer panel on the left side of the page, right click an instance and, from the
popup menu, select Properties, as shown in Figure 12 (page 19).
Using HP ESO
Figure 12 Selecting Analysis Services properties
4.
In the Analysis Server Properties popup, select Security from the Select a page panel on the
left, as shown in Figure 13 (page 20).
Configuration steps prior to using HP ESO
19
Figure 13 Analysis Server Properties page
5.
6.
7.
8.
If the account to be used to connect to the Analysis Services instance is not listed, click Add….
Enter the account to be added then click OK.
Close the Analysis Server Properties window.
Repeat steps 2 through 7 for all Analysis Services instances so that HP ESO can optimize the
resources based individual workloads.
Getting Started
When first run, HP ESO displays the Introduction page as shown in Figure 14 (page 21). The
Introduction page is one of two Getting Started pages; the other is the SQL Server Login page. The
SQL Server Login page displays when you start an Administrator Session. The left navigation pane
displays links to these and other HP ESO pages. To use these pages, you must start an Administrator
Session, as described in “Creating an authenticated Administrator Session (Admin Session)”
(page 25).
20
Using HP ESO
Figure 14 HP ESO Introduction page
IMPORTANT: After starting an HP ESO software Admin Session, HP highly recommends that you
first go to the Data Collection page to configure and start data collection, as directed in “Quick
start: basic session” (page 21). Data collection enables HP ESO to capture and analyze real SQL
Server workload patterns in the system and to give the best optimization recommendations, based
on the observed workload patterns. For more information, see “Data Collection page: Collecting
data for analysis and optimization recommendations” (page 27).
Quick start: basic session
To begin using HP ESO, follow these steps:
Getting Started
21
1.
Start an exclusive HP ESO Administrator Session (Admin Session) by clicking Enter Admin
Session in the upper left corner of the left pane of the HP ESO Introduction page (see Figure 15
(page 22)).
Figure 15 Enter Admin Session on HP ESO Introduction page
NOTE: Before you can use HP ESO pages and functionality, you must perform this step. For
more information about Admin Session, see “Creating an authenticated Administrator Session
(Admin Session)” (page 25).
Clicking Enter Admin Session brings up the SQL Server Login page (for a sample view of the
SQL Server Login page and more information, see “SQL Server Login: Setting credentials and
logging into SQL Server and Analysis Services instances” (page 25)).
2.
Specify SQL credentials in the SQL Server Login page and then log in to SQL Server and
Analysis Services instances using the specified credentials. As shown in Figure 16 (page 22),
you have two options for entering credentials:
Option 1 — Specify the same credentials once and for all
Option 2 — Specify specific credentials for each instance
After specifying the credentials, log in to the instances by clicking Connect.
Figure 16 Connect button and session timeout features
3.
22
View various SQL settings by selecting the links in the left pane of the page, as shown in
Figure 17 (page 23) (in Figure 17 (page 23), the SQL Server Login page is currently selected).
Using HP ESO
Figure 17 Left pane page selection links
4.
5.
Configure and perform data collection. To do so, access the Data Collection page by selecting
the Data Collection link (the Data Collection link is the first link below the SQL Server Login
link). The data collection process generates recommendations. Before performing data
collection, make sure all the SQL instances are under the workload stress expected in real
world conditions. For more information about data collection, see “Data Collection page:
Collecting data for analysis and optimization recommendations” (page 27).
View optimization recommendations by accessing any of the Optimizations pages (connect
to any of the links under Optimizations in the left pane of the page).
IMPORTANT: To ensure suitability of HP ESO’s optimization recommendations, perform data
collection during typical business workloads. To obtain the most up-to-date recommendations,
run and complete (stop) the data collection process immediately prior to accessing the reports
page.
6.
View data collected by the data collection process by accessing the Workload and Performance
History reports page. For more information, see “Workload and Performance History”
(page 49).
NOTE: To obtain the most up-to-date reports, run and complete (stop) the data collection
process immediately prior to accessing the reports page.
Getting Started
23
7.
Whenever the HP ESO Admin Session is about to expire (in Figure 18 (page 24), the Time
left field indicates two minutes are left before session expiration), click Extend Session to reset
the timeout value. When less than one minute remains, some pages might not be accessible.
Clicking Extend Session makes those pages accessible again.
Figure 18 Session timer and Extend Session button
The default Admin Session timeout is 30 minutes. You can change the timeout value in the
ESO Session Configuration section of the SQL Server Login page. To see this section, you might
have to scroll down to the bottom of the SQL Server Login page. Figure 19 (page 24) shows
the ESO Session Configuration section. For more information, see “SQL Server Login: Setting
credentials and logging into SQL Server and Analysis Services instances” (page 25).
Figure 19 ESO Session Configuration: Session Time Out
8.
To end the ESO Admin Session, click Exit Session (directly beneath the Time left field). For
security purposes, this clears all SQL credentials. You need to re-enter SQL credentials when
running HP ESO again. When an HP ESO Admin Session expires, all SQL credentials are
cleared automatically and must be re-entered.
Floating help
Anytime you mouse over a setting or section that has a cursor/question mark symbol ( ), clicking
that symbol brings up floating help text, as shown in Figure 20 (page 24). This feature is extremely
useful in learning about the many settings that HP ESO provides.
Figure 20 Floating help text
24
Using HP ESO
You can also access HP ESO online help by accessing the Online Help page, as described in
“Online help” (page 54).
Creating an authenticated Administrator Session (Admin Session)
An Administrator session is created to ensure that only one authenticated user can use and change
the different parameters in the system and the SQL Server. When an Admin Session is started by
a user, other users will be blocked from accessing the ESO pages.
Before using ESO, make sure to start an Admin Session by clicking Enter Admin Session on the
top left corner of the page (see Figure 21 (page 25)). This will start an exclusive session for the
current SMH user that will last for 30 minutes by default. The session time limit may be reset to the
full 30 minutes by clicking Extend Session. The number of minutes remaining in the current session
will be shown at the Time Left field. If the time left reaches 0, you need to start an Admin Session
again to continue working on ESO. An “In Admin Session” message indicates that an Admin
Session is currently active.
NOTE: The default session timeout of 30 minutes is configurable and may be overridden by
entering the new timeout value in the New Value field in the ESO Session Configuration section of
the SQL Server Login page. For more information, see “Modifying the Admin Session timeout value”
(page 27).
If an Admin Session has not been started, the system will display detailed steps for starting a
session, as shown in Figure 21 (page 25).
Figure 21 Steps to enter an Admin Session
SQL Server Login: Setting credentials and logging into SQL Server and Analysis
Services instances
Upon starting an Admin Session, the SQL Server Login page appears, as shown in Figure 22
(page 26). The page displays all SQL Server and Analysis Services instances along with input
boxes for entering login credentials. This page allows you to enter login credentials and the
Getting Started
25
authentication type for each instance. From this page, you can then log in to the SQL Server and
Analysis Services instances. HP ESO validates the credentials.
Figure 22 SQL Server Login page
For SQL Server instances, the type of login (Windows Authentication or SQL Authentication) can
be selected under the Authentication Type column. For Analysis Services, Windows Authentication
is the only selectable option.
Username and Password columns contain the appropriate input boxes to fill in the user name and
password used for logging into each SQL Server instance and Analysis Services instance.
If similar login credentials will be used to log in to all SQL Server and Analysis Services instances,
you can have the same login credentials applied to all the instances. Simply fill in the Authentication
Type, Username, and Password boxes in the top All Instances row.
Finally, click Connect to log into the SQL instances using the provided login credentials. As shown
in Figure 23 (page 27), the Login Status and Login Type : Login Name columns indicate the validity
of the supplied login credentials and the type of authentication (Windows or SQL Authentication),
respectively.
If a login fails, the Latest Login Log section shows the reason for the failure, as shown in Figure 23
(page 27).
For security purposes, when an ESO Admin Session ends or expires, all SQL credentials are cleared.
You must re-enter SQL credentials with each new session.
26
Using HP ESO
Figure 23 Login credentials status
Modifying the Admin Session timeout value
The default session timeout of 30 minutes may be changed by entering the new timeout value in
the New Value field under the ESO Session Configuration section of the SQL Server Login page.
The maximum timeout value is approximately 35791 minutes. The ESO Session Configuration
section is near the bottom of the page; you might have to scroll down to that section. Figure 24
(page 27) shows the ESO Session Configuration section where the session timeout can be modified.
NOTE: When there is less than one minute remaining in the current Admin Session, some pages
might be inaccessible. To resolve the issue, click Extend Session (located at the top of the left pane
of the page).
Figure 24 ESO Session Configuration: Session Time Out
Settings pages
Use the Settings pages to configure some of your settings prior to discovery and optimization of
the HP server, the Windows Operating System (OS), and SQL Server.
Data Collection page: Collecting data for analysis and optimization recommendations
The data collection feature collects data from the Windows OS, SQL Server Database Engine, and
Analysis Services. Data includes CPU, memory, and IO utilization; and SQL Server transaction
rates. Collected data is saved in the form of CSV (Comma Separated Value) files located at
%ProgramFiles%\McPerfOpt\Data, as shown in Figure 25 (page 28).
Settings pages
27
Figure 25 CSV data files
These CSV files are used by HP ESO for analysis, and form the basis of its optimization
recommendations and its performance and workload history reports.
IMPORTANT: To ensure suitability of HP ESO’s optimization recommendations, perform data
collection during typical business workloads.
Click Data Collection in the HP ESO navigation pane to display the Data Collection page. Figure 26
(page 28) shows a Data Collection page. This page allows you to set data collection parameters
and to start the data collection process.
Figure 26 Data Collection page
28
Using HP ESO
User input fields in the Data Collection Settings section include the following:
•
START ON ⇒ Lets you select the date and time that data collection starts. NOW is the default
value and immediately starts data collection when you click Start. To specify a future date
and time for starting data collection, click the calendar icon ( ).
•
STOP ON ⇒ Lets you select the date and time when data collection stops. NON-STOP is the
default value and keeps data collection running until you stop it manually.
•
Data Sampling Rate ⇒ Lets you specify how often data is sampled by data collection. The
default value is 10 seconds.
NOTE: The lower the sampling rate value, the finer the resolution of the data samples, and
the more accurate the internal data analysis will be. However, setting the sampling rate too
low makes the resulting data collection files larger. The higher the sampling rate value, the
coarser the resolution of data samples, and the less accurate the internal data analysis will
be. However, setting the sampling rate higher will make the resulting data collection files
smaller.
Control buttons in the Data Collection Settings section include the following:
•
START ⇒ Starts data collection on the selected date and time in the START ON field.
•
STOP ⇒ Stops data collection on the selected date and time in the STOP ON field.
When these buttons are disabled, they display as grayed-out.
When data collection starts, HP ESO automatically invokes the Windows Performance Monitor
tool (see Figure 27 (page 29)) to collect data from different counters. To view data collected by
the data collection process, use the Workload and Performance History reports page, as described
in “Workload and Performance History” (page 49).
NOTE: To obtain the most relevant and up-to-date workload and performance history reports,
perform the data collection process and complete (stop) it immediately prior to accessing the reports
page.
Figure 27 Performance Monitor
Optimizations pages
The Optimizations pages provide various types of optimization recommendations based on collected
data.
Optimizations pages
29
IMPORTANT: HP highly recommends that you run data collection and complete the process
before visiting or modifying the Optimization pages. To ensure suitability of HP ESO’s optimization
recommendations, perform data collection during typical business workloads.
HP ESO optimization pages typically display the following values or controls (see Figure 28
(page 30)):
•
N/A ⇒ No recommendation can be provided for the parameter at the current state and
environment.
•
Current ⇒ The current parameter value discovered in the system.
•
Recommended ⇒ The parameter value recommended by HP ESO.
•
New Value ⇒ This field contains the new parameter value to be applied to the system. By
default, this field contains the recommended value. However, you can change this value if
desired.
•
SET ALL ⇒ Sets all of the parameters shown in the New Value field on the page. Click this
button to make the changes take effect immediately. Changes requiring a system or SQL Server
service restart are indicated after the changes are applied.
•
SET ⇒ Sets the specific parameter shown beside it. Click this button to make the change take
effect immediately. Changes requiring a system or SQL Server service restart are indicated
after the change is applied.
•
Enable Parameter Change check box (alongside each parameter name) ⇒ When checked,
allows the corresponding parameter to be changed. When unchecked, the parameter retains
its current value after clicking SET or SET ALL.
•
Select/Unselect All check box ⇒ When checked, causes the parameter changes enablement
check boxes under its section to toggle between Selected and Unselected.
•
Expand (
•
Show Recommendation Details check box ⇒ Shows details of all recommendations, as shown
in Figure 28 (page 30). The details are listed under the parameter setting area.
) and Collapse (
) ⇒ Expand or Collapse a section in a page.
Figure 28 Show Recommendation Details page
When a critical error occurs, the Optimizations page displays possible steps that can be taken,
as shown in Figure 29 (page 31).
30
Using HP ESO
Figure 29 Critical error page
SQL Server page: Viewing and enabling SQL Server and Analysis Services
optimization recommendations
The SQL Server page contains recommendations for setting parameters for SQL Server and Analysis
Services instances. The SQL instances displayed on the page are grouped into the following types:
•
•
SQL Server instances
◦
Database Engine (OLTP)
◦
Data Warehouse (DW)
◦
SAP Database Engine
Analysis Services instances
Figure 30 (page 32) shows an example of the SQL Server page.
Optimizations pages
31
Figure 30 SQL Server page
The following subsections describe the parameters affecting SQL Server optimization.
NOTE: For information about affinity settings, see “CPU page: Viewing and enabling CPU
assignment optimization recommendations” (page 41).
SQL Server database instance parameters
NOTE: Cluster-related parameters (Cluster Network Name, Computer Name, Status, and Computer
Role) are described in “Clustered SQL Server instance” (page 40).
Maximum Degree of Parallelism
When SQL Server runs on a system with more than one microprocessor or CPU, it detects the best
degree of parallelism. Specifically, it recognizes the number of processors employed to run a single
statement, for each parallel plan execution. Use the Maximum Degree of Parallelism (MAXDOP)
option to limit the number of processors to use in parallel plan execution.
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.
32
Using HP ESO
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
Figure 31 Setting the Xp_CmdShell option
Analysis Services instance parameters
Flight Recorder
SQL Server Analysis Services Flight Recorder provides a mechanism to record server activity into
a short-term log. Information captured by Flight Recorder can be helpful for troubleshooting specific
issues; however the load placed on the server when capturing the snapshots and trace events can
have a small impact on overall performance. For optimal performance, the flight recorder should
be disabled unless attempting to capture diagnostic information relevant to troubleshooting a
specific problem.
Random File Access
A Boolean property that indicates whether database files and cached files are accessed in random
file access mode. This property is disabled by default. By default, Analysis Services does not set
the random file access flag when opening partition data files for read access. On high-end systems,
particularly those with large memory resources and multiple NUMA nodes, it can be advantageous
to use random file access. In random access mode, Windows bypasses page mapping operations
that read data from disk into the system file cache, thereby lowering contention on the cache.
Available only on SQL 2012 and later.
LowMemoryLimit
Specifies the amount of memory allocated by Analysis Services at startup. When this limit is reached,
the instance starts to slowly clear memory out of caches by closing expired sessions and unloading
unused calculations. The server will not release memory below this limit. The default value is 65,
which indicates the low memory limit is 65% of physical memory or the virtual address space,
whichever is less.
TotalMemoryLimit
Defines a threshold that, when reached, causes the server to deallocate memory more aggressively.
The default value is 80% of physical memory or the virtual address space, whichever is less.
CoordinatorQueryBalancingFactor and CoordinatorQueryBoostPriorityLevel
When multiple users access SQL Server Analysis Services concurrently, an expensive query that
needs to scan large number of partitions can monopolize the system and block other users. To
avoid this problem and achieve high concurrency, HP recommends that
CoordinatorQueryBalancingFactor be set to 1 and CoordinatorQueryBoostPriorityLevel to 0.
EnableRolapDistinctCountOnDataSource
Queries that include DistinctCount in a ROLAP process can run faster, assuming certain criteria
are met. Performance is improved because more of the operation has been off-loaded to the
relational database engine, where COUNT(DISTINCT column) is used to return unique non-null
values, eliminating the need for more expensive ordering operations that degrade query
performance. This optimization is disabled by default because the query results produced by the
34
Using HP ESO
new and older algorithms are not always identical. Transact-SQL counting can vary for NULL values
and different collations. If you want to use the optimization, set the
OLAP\ProcessPlan\EnableRolapDistinctCountOnDataSource property to 1.
Database page: Viewing and enabling database optimization recommendations
The Database page contains parameters related to database files in each SQL Server and Analysis
Services instance. The SQL instances displayed on the page are grouped into the following types:
•
•
SQL Server instances
◦
Database Engine
◦
Data Warehouse
◦
SAP Database Engine
Analysis Services instances
Figure 32 (page 35) shows an example of the Database page.
Figure 32 Database page
When Availability Groups and database mirroring are in use, the Database page displays
information about them. Availability Groups and database mirroring contribute to higher availability
and more reliable disaster recovery for databases. For more information about availability groups,
database mirroring, and viewing information about high availability and disaster recovery
configurations, see “Database page: Viewing high availability and disaster recovery configurations”
(page 37).
The following subsections describe database parameters and recommendations that might be seen
on the Database optimization page. Parameters pertaining to Availability Groups and database
mirroring are described in “Database page: Viewing high availability and disaster recovery
configurations” (page 37). Cluster-related parameters (Cluster Network Name, Computer Name,
Status, and Computer Role) are described in “Clustered SQL Server instance” (page 40).
Optimizations pages
35
SQL Server Database Engine properties
File Growth
The File Growth option specifies the method of incremental allocation applied when an operating
system file is extended. Possible values are OFF, MB, or % (Percent). SQL Server files can grow
automatically from their originally specified size. When you define a file, you can specify a specific
growth increment. Every time the file is filled, it increases its size by the growth increment. If there
are multiple files in a file group, they will not automatically grow until all the files are full. Growth
then occurs in a round-robin fashion. If necessary, the tool recommends allocation of larger space
in the file and turns off automatic file growth.
Auto Create Statistics
When you enable the AUTO_CREATE_STATISTICS option, the Query Optimizer creates statistics
on individual columns used in a predicate, if these statistics are not already available. These
statistics are necessary to generate the query plan. They are created on columns that do not have
a histogram in an existing statistics object.
Auto Update Statistics
Updates query optimization statistics on a table or indexed view. By default, the query optimizer
already updates statistics as necessary to improve the query plan; in some cases, you can improve
query performance by using UPDATE STATISTICS or the stored procedure sp_updatestats to update
statistics more frequently than the default updates.
Updating statistics ensures that queries compile with up-to-date statistics. However, updating statistics
causes queries to recompile. HP recommends that you avoid updating statistics too frequently:
there is a performance trade-off between improving query plans and the time it takes to recompile
queries. The specific trade-offs depend on your application. UPDATE STATISTICS can use tempdb
to sort the sample of rows for building statistics.
Auto Update Statistics Async
When this option is enabled, the SQL Server will start updating statistics asynchronously, using a
separate background thread. Client queries will not have to wait for the process to complete, and
they can continue using the current statistics while the update is processing in background. When
the update process completes, the Query Optimizer can start using the updated statistics. This
means that until the update process is complete, the Query Optimizer will produce execution plans
based on the current/old statistics.
Analysis Services properties
Data Dir
The Data Dir property specifies where Analysis Services data is stored per server instance.
Temp Dir
The Temp Dir property specifies where Analysis Services places temporary files that it uses during
processing operations.
Log Dir
The Log Dir property specifies where Analysis Services logs and traces are stored.
Backup Dir
The Backup Dir property specifies where Analysis Services backups are stored by default.
36
Using HP ESO
Measure Group
A Measure Group (MeasureGroup object) is composed of basic information, measures, dimensions,
and partitions.
•
Basic information includes the name of the measure group, the type of measures, the storage
mode, the processing mode, and others.
•
Measures are the actual set of measures that compose the measure group. For each measure
there is a definition for the aggregate function, the formatting attribute, the data item source,
and others.
•
Dimensions are a subset of cube dimensions used for creating the processed measure group.
•
Partitions are the collection of physical splits of the processed measure group.
Partition
A partition is a container for a portion of the measure group data. Partitions are not seen from
MDX queries; all queries reflect the whole content of the measure group, regardless of how many
partitions are defined for the measure group. The data content of a partition is defined by the
query bindings of the partition and by the slicing expression.
Estimated Rows
The estimated number of rows in the partition.
Estimated Size
The estimated size of the partition in megabytes.
Proactive Caching
Proactive caching provides automatic MOLAP cache creation and management for OLAP objects.
The cubes immediately incorporate changes that are made to the data in the database, based
upon notifications received from the database. The goal of proactive caching is to provide the
performance of traditional MOLAP, while retaining the immediacy and ease of management offered
by ROLAP.
ESO database recommendation statements
Database File on System Drive
HP ESO recommends that you store the database file in a different location than the system or OS
drive. If a database file is found on the system drive, HP ESO's recommendation to relocate the
file displays on this page.
Multiple Database File on a Drive
HP ESO also recommends that the database files are located on a dedicated drive. If multiple
database files are found on a drive, HP ESO's recommendation for relocating them on separate
drives displays on this page.
Database page: Viewing high availability and disaster recovery configurations
HP ESO can provide information about availability and disaster recovery configurations for SQL
Server and Analysis Services databases.
Availability Group
An Availability Group, a feature introduced with SQL Server 2012, provides high availability for
application databases. Availability Groups support a failover environment for a discrete set of user
databases known as availability databases. An Availability Group provides all the benefits of
Database Mirroring but also comes with a powerful set of new options that increase application
Optimizations pages
37
availability. More importantly, the Availability Group feature includes support of active secondary
replicas, which dramatically improves resource utilization. Active secondary replicas perform log
backups and copy-only backups of a full database, file, or filegroup.
If a database is a member of an Availability Group, additional parameters will be displayed,
including Availability Group Name, Synchronization Status, and Replica Role. Figure 33 (page 38)
shows a sample portion of the Database page screen displaying information about Availability
Group parameters. The Replica Role is indicated within parenthesis next to the Availability Group
Name. For example, in Figure 33 (page 38), the Availability Group Agroup_SP1 is a primary
replica. Table 2 (page 38) and Table 3 (page 38) list possible synchronization states and replica
roles, respectively. Possible database status and read-only values are listed in the next subsection
in Table 4 (page 39) and Table 5 (page 39), respectively.
Figure 33 Database in Availability Group
Table 2 Possible synchronization status values
Value
Description
NotSynchronizing
The synchronization state is Not Synchronizing.
Synchronizing
The synchronization state is Synchronizing.
Synchronized
The database replica is synchronized with the primary.
Reverting
The database replica is reverting after a failover.
Initializing
The principal database is initiating a failover.
Table 3 Possible replica roles
Role
Description
Resolving
The Role is Resolving.
Primary
The Role is Primary.
Secondary
The Role is Secondary.
Unknown
The Role is Unknown.
Mirrored database
Database mirroring is used for protecting application databases from planned and unplanned
downtime. Combined with log shipping and failover clustering, database mirroring effectively
meets high availability requirements of mission critical applications. A mirror database is a copy
of the primary database and typically is fully-synchronized with it. When the transaction log buffer
for the principal database is written to disk, transactions are sent directly from the principal database
and server to its mirror database and server.
If a database is configured for mirroring, Mirror Status information will be displayed, as shown in
Figure 34 (page 39). Possible values for are listed in Table 6 (page 39). Table 4 (page 39) and
Table 5 (page 39) list possible values for Database Status and Read-Only, respectively.
38
Using HP ESO
Figure 34 Mirrored database
Table 4 Possible database status values
Value
Description
Normal
The database is available.
Restoring
The database is going through the restore process.
RecoveryPending
The database is waiting to go through the recovery process.
Recovering
The database is going through the recovery process.
Suspect
The database is has been marked as suspect. You should check your data, and the database
might have to be restored from a backup.
Offline
The database has been taken offline.
Standby
The database is in standby mode.
Shutdown
The server on which the database resides has been shut down.
EmergencyMode
The database is in emergency mode.
AutoClosed
The database has been automatically close.
Inaccessible
The database is inaccessible. The server might be switched off or the network connection
has been interrupted.
Table 5 Possible read-only values
Value
Description
False
The database is read-write.
True
The database is read-only.
Table 6 Possible mirror status values
Value
Description
None
The principal database is not mirrored.
Suspended
Mirroring of the principal database is suspended.
Disconnected
The principal database and the mirror database are disconnected.
Synchronizing
The principal database and the mirror database are in the process of synchronizing.
PendingFailover
The principal database is initiating a failover.
Synchronized
The principal database and the mirror database are synchronized.
Optimizations pages
39
Clustered SQL Server instance
If an SQL Server is clustered, cluster status information will be displayed, including Cluster Network
Name, Status, Computer Role, and Computer Name, as shown in Figure 35 (page 40). (This
example shows a portion of the page; in full view, the Computer Name would be seen to the right
of the Computer Role.) Information about these status parameters is included in the subsections
that follow.
Figure 35 Clustered database
Cluster Network Name
Cluster Network Name is the virtual host name of a clustered system. This name is also used to
reference the default SQL Server instance in a clustered system.
Computer Name
Computer Name is the computer host name of the physical node in a clustered system.
Status
Status is the current status of the cluster. For possible values and descriptions, see Table 7 (page 40).
Table 7 Possible cluster status values
Value
Description
Unknown
The instance of SQL Server is in an unknown state.
Online
The instance of SQL Server is online.
OnlinePending
The instance of SQL Server is waiting to come online.
Offline
The instance of SQL Server is offline.
OfflinePending
The instance of SQL Server is waiting to go offline.
Computer Role
Computer Role is the current role of the computer node in a cluster. For possible values and
descriptions, see Table 8 (page 40).
Table 8 Possible computer roles
Role
40
Description
Unknown
The Role is unknown.
Not Applicable
There is no Role applicable in the current setup.
Primary
The Role is primary.
Secondary
The Role is secondary.
Using HP ESO
CPU page: Viewing and enabling CPU assignment optimization recommendations
The CPU page (see Figure 36 (page 41)) displays SQL Server affinity settings and recommendations
for each SQL instance in the system. To carry out multitasking, Microsoft Windows sometimes
moves process threads among different processors. Although this is efficient from an OS point of
view, this activity can reduce SQL Server performance under heavy system loads, as each processor
cache is repeatedly reloaded with data. Assigning processors to specific threads can improve
performance under these conditions by eliminating processor reloads and reducing thread migration
across processors (thereby reducing context switching). Such an association between a thread and
a processor is called processor affinity.
HP ESO generally recommends that you confine SQL instances with relatively light workloads to
under-utilized CPUs. This results in some SQL instance affinities being assigned an unusually high
order, or non-contiguous logical CPU number. Similarly, SQL Server and the operating system
automatically manage the CPU affinities of highly-utilized SQL instances. This logic results in less
conflict over CPU resources among under- and highly-utilized SQL instances.
Figure 36 CPU page
The following subsections describe parameters pertaining to CPU affinity and performance
optimization.
SQL Server affinity
On multi-processor systems, SQL Server interaction with CPU resources can be controlled by setting
the affinity mask options. Configuring these options results in SQL Server threads being scheduled
to run on the same processor each time they run. If you do not configure these options, the threads
can migrate among processors. In SQL Server 2008 R2, you can set SQL Server Affinity to a
maximum of 256 CPUs. In older versions of SQL Server, this setting is limited to only 64 CPUs.
Optimizations pages
41
NOTE: Do not set SQL Server Affinity and IO Affinity to the same CPUs because it can degrade
system performance (HP ESO displays a warning if the system is configured this way). As a general
rule, HP ESO recommends affinity on only a few specific processors for SQL instances that are
comparatively lightly utilized, so they do not use all of the available system processors. Likewise,
HP ESO does not recommend CPU Affinity for heavily utilized SQL instances, so they can use all
of the available system processors.
From a single GUI interface, processor affinity can be set for both SQL Database Engine and
Analysis Services Engine, for all the instances in the server. This reduces the complexity of setting
instance affinity one-by-one. In addition to the CPU/NUMA information shown in the SSMS GUI,
HP ESO also shows the Processor Group information. This helps the user allocate resources properly,
based on application needs (some applications might not be using all Processor Group information).
Analysis Services Process GroupAffinity
To support multiple processor groups and thus more than 64 CPUs, SSAS 2012 was updated to
set the process affinity mask for the msmdsrv.exe process to span multiple processor groups.
Along with this capability, a new configuration property named GroupAffinity was added for each
thread pool in the server. This property allows an SSAS administrator to have fine-grain control
over which CPUs on a machine are used for each thread pool managed by Analysis Services. The
GroupAffinity setting is a bitmask that determines which CPUs in a processor group can be used
for the thread pool in which the GroupAffinity mask is defined.
Storage page: Viewing and enabling storage optimization recommendations
The Storage page displays recommendations for different storage parameters. Figure 37 (page 42)
shows an example of a Storage page.
Figure 37 Storage page
The following subsections describe the parameters affecting storage optimization.
Database RAID level
HP highly recommends that tempdb files and log files for user databases be on physical disks with
RAID 1 + 0 or RAID 1.
42
Using HP ESO
User Write Cache Setting
This setting enables write caching to improve disk performance, but a power outage or equipment
failure might result in data loss or corruption.
User Cache Power Protection
Some storage controllers provide an option to enable cache power protection. Using a backup
battery, a storage controller can keep data in volatile memory intact, even during power
interruptions. This protects cached data even during power failures.
Drive free space
When drive free space reaches less than 20%, a Warning message displays, with a
recommendation to either move the file to a larger drive or free up more space on the current drive.
Volume mount point
Volume mount points are specialized file system objects which are used to mount and provide an
entry point to other volumes. Mount points can be created in a directory on a file system, which
gives a reference to the root directory of the mounted volume. HP ESO will show all mount points
on disk with volume mount point configured.
Network page: Viewing and enabling network optimization recommendations
The Network page includes controls for setting network interface NUMA Node, Interrupt, and Port
affinities. Figure 38 (page 43) shows an example of a Network.
Figure 38 Network page
The following subsections describe the parameters affecting network optimization.
NUMA node affinity
NUMA (Non Uniform Memory Access) Node is a logical grouping of processors that share common,
directly-linked physical memory. HP ESO recommends CPU NUMA Nodes closest to the network
interface I/O.
Optimizations pages
43
Interrupt affinity
Network interface interrupt affinity settings include All Close CPUs, One Close CPU, or All CPUs.
HP ESO recommends All Close CPUs in most cases.
Port affinity
SQL Server uses an application port (usually Port 1433) whose affinity can be set to one or more
CPU NUMA Nodes. As with SQL CPU Affinity, this improves performance by directing network
traffic bound to a CPU or group of CPUs used by SQL Server. Additional ports can also be added
and removed.
To delete a specific network port, follow these steps:
1. Select the IP address of the port to be deleted.
2. Clear all boxes, along with that port number box.
3. Click Set.
To delete all ports associated with an IP address, follow these steps:
1. Select the desired IP address.
2. Click Delete Port until all entries are removed.
3. Click Set.
NOTE:
Any changes you make in the Network page will not take effect until the system is rebooted.
Receive-Side Scaling
Receive-Side Scaling (RSS) resolves the single-processor bottleneck by allowing the receive-side
network load from a network adapter to be shared across multiple processors. RSS enables packet
receive processing to scale with the number of available processors. This allows the Windows
Networking subsystem to take advantage of multi-core processor architecture.
Received-side scaling is enabled by default in Windows Server 2008 and Windows Server 2008
R2. To take advantage of RSS, network drivers must be written with RSS capabilities. Currently,
RSS cannot make use of more than 64 processors with Windows 2008 R2, even with Service Pack
1, released in February 2011.
Modern network drivers are configured to use RSS through settings found in the Windows Device
Manager, in the Advanced Properties of the network interface. Depending on the driver versions
and OS versions, HP ESO might not support some of the RSS features. Contact HP support for
details.
HP ESO recommends that RSS be enabled as necessary. The following parameters of every Network
Interface will have corresponding RSS recommended settings:
•
Base Processor — The first logical CPU number to be used for RSS.
•
Max RSS Processors — The maximum number of logical processors to be used for RSS of the
network interface.
•
RSS Ring (also known as RSS Queue) — The maximum number of CPUs a NIC can support
for RSS. The number of RSS CPUs on a system would be capped by the MaxNumRssCpus
registry key or the RSS ring NIC property setting, whichever is the lowest.
Figure 39 (page 45) shows the Network page view of RSS parameter optimization
recommendations.
44
Using HP ESO
Figure 39 RSS settings in Network Affinity page
SQL Startup Option page: Viewing and enabling startup options
A set of default startup options is written to the registry during SQL Server installation. 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 40 (page 45) shows an example of the SQL Startup Option
page. The subsections that follow describe the trace flag startup options.
Figure 40 SQL Startup Option page
This Startup Option page provides a tab for each particular SQL instance. Clicking a tab displays
the trace flags available for that particular SQL instance.
Trace flags are very sensitive to the SQL Server edition and versions. Only trace flags supported
by the SQL instance are shown on the page with status. The page displays a description of each
supported trace flag.
Optimizations pages
45
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 in order to reduce
costs when you have too many CPUs per NUMA node.
Trace flag 834
When combined with the Lock Pages in Memory 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 where the SQL Server is the main (or only) application running.
Trace flag 1117
Trace flag 1117 determines how the SQL Server automatically extends (grows) data files in a file
group when automatic file growth is needed. Enable trace flag 1117 to cause the SQL Server to
automatically grow all of the files at the same time. Otherwise, the files will automatically grow in
round-robin fashion.
Trace flag 1118
Trace flag 1118 is used to help alleviate allocation bitmap contention in tempdb when under a
heavy load of small temp table creation and deletion.
Trace flag 2371
Trace flag 2371 is used to address the well-known problem caused by the current 20% threshold
that determines when automatic statistics updates occur. The statistics keep track of the number of
changes made to a table. The threshold is the percentage of the number of rows in the table. When
the number of changes exceed 20% of the number of rows in the table, the statistics are
automatically updated. For large applications with correspondingly large tables, this could mean
that automatic updates would not occur often enough to accurately reflect current statistics. As a
result, administrators would have to manually update the statistics (using a query plan, for example).
Because the manual updates usually require excessive I/O, this was not optimal for many
applications. The 2371 trace flag changes the threshold from a fixed-rate of 20% to a dynamic
rate based on the table size. The higher the number of rows in the table, the lower the threshold
will become to trigger an update of the statistics. Enable the 2371 trace flag to prevent the need
for manually updating the statistics.
NOTE: To prevent small tables from being updated too frequently, automatic updates require a
minimum of 500 rows in a static table and 6 rows in a temp table.
Trace flag 2549
The DBCC CHECKDB checks the logical and physical integrity of all objects in the specified database.
The command builds an internal list of pages to read per unique disk drive across all database
files. The logic determines unique disk drives based on the drive letter of the physical file name of
each file. If the underlying disks are actually unique when the drive letters are not, the DBCC
CHECKDB command treats these database files as residing on one disk. Enable the trace flag to
optimize the CHECKDB process by treating each database file as residing on a separate, unique
disk drive. Do not use this trace flag unless you know that each file is based on a unique physical
disk.
46
Using HP ESO
Trace flag 2562
By default, the DBCC CHECKDB command tries to minimize the amount of tempdb resources
required to check the entire database. The command does this by breaking up the database into
batches. This reduces the number of indexes or "facts" that it generates. Trace flag 2562 implements
the following changes:
•
Forces the DBCC CHECKDB command to run all processing in a single batch regardless of the
number of indexes in the database.
•
Improves the internal process for determining which pages to read from the database. This
reduces contention on the DBCC_MULTIOBJECT_SCANNER latch, helping avoid such errors
as:
Timeout occurred while waiting for latch: class ‘DBCC_MULTIOBJECT_SCANNER’.
One effect of using this trace flag is that the space requirements for tempdb may increase. The
tempdb may grow to as much as 5% or more of the user database that is being processed by the
DBCC CHECKDB command. Therefore, to avoid automatic growth when you use this trace flag,
which may slow down the performance of the DBCC CHECKDB command, HP recommends that
you pre-size tempdb to at least 5% of your database size.
System page: Viewing and enabling system optimization recommendations
The System page displays information about add-on PCI controllers; settings of Software Discovery
(“Configuring and initiating Software Discovery” (page 48)); and status of system software, drivers,
and firmware versions. The page shows the result of the software discovery process. Figure 41
(page 47) shows an example of a System page.
Figure 41 System page
PCI Controller Information
This section of the page enumerates all of the system's add-on PCI cards. It also indicates when
PCI cards are inserted in slots that are incapable of utilizing their maximum capabilities. If
better-suited slots are available, HP ESO recommends them by slot number.
Optimizations pages
47
Software Discovery
This section allows you to specify the source (Reference Catalog Location) for Software Discovery
and to run Software Discovery. The Reference Catalog is a file that lists details about system software
and firmware components, including information about the latest available versions of the
components. For more information, see “Configuring and initiating Software Discovery” (page 48).
System software and firmware status
This section of the page lists (from the Reference Catalog) the status of software and firmware
components, as shown in the example in Figure 42 (page 48). The table describes each component
and indicates the latest available version of the component and the component status (whether it
is up to date or needs to be upgraded).
Figure 42 System software and firmware status
Configuring and initiating Software Discovery
HP ESO's Software Discovery feature checks to see if the latest HP software, drivers, and firmware
are installed in the system. The Optimization section’s System Software page includes a Software
Discovery section that allows you to select the location for the Software Discovery Reference Catalog
and to initiate the Software Discovery process.
Possible choices for the location of the Software Discovery Reference Catalog are:
•
Web ⇒ HP ESO connects to an HP File Transfer Protocol (FTP) site (ftp.hp.com) to get the latest
catalog. Internet connectivity is required.
•
Local ⇒ Lets you specify a system location for the HP catalog file. When selected, you are
prompted for the ProLiant Support Pack (PSP) Catalog location to use for software discovery.
Specify a directory that contains the PSP and HPSUM components and that is on the system
on which HP ESO is running. The logged-in account for the current Microsoft Windows session
must have access to the specified local directory.
NOTE: When Local is selected, specifying a shared network drive causes the software discovery
to fail by default. To work around this issue, copy the catalog file to a non-networked drive (for
example, C:).
If you must use a network drive, use SysinternalsSuite by Mark Russianovich (http://
technet.microsoft.com/en-us/sysinternals/bb842062.aspx). PSEXEC is the only tool needed.
Perform the following steps:
1. Open up a new command window and run: psexec -s cmd.exe
2. Run the net use command or any other script to create the network drive.
Clicking the Software Discovery RUN button runs the system software discovery and updates.
Results are shown on the same page (in the Optimization section’s System Software page). Status
of the latest discovery also displays below this button.
48
Using HP ESO
NOTE:
Software Discovery executes every time the server restarts.
In the System page’s Software Discovery section, when C:\ is entered in Proliant Support Pack
Catalog Location, the message “The last discovery on MMDDYY-Time” will be displayed even if
there is no valid catalog file in the C:\ location. When specifying C:\ as the location of a catalog
file, make sure the file does exist in that location.
Reports pages
Reports pages include the Workload and Performance History page and the Save/Rollback SQL
Configuration page.
Workload and Performance History
Use the Workload and Performance History page to select and view data collected by the data
collection process (the data collection process is described in “Data Collection page: Collecting
data for analysis and optimization recommendations” (page 27)). Figure 43 (page 49) shows an
example of a Workload and Performance History report. You can view a graph of the data
collected, save the data to a file, and compare graphs of two different data collection sources.
Figure 43 Workload and Performance History page
To view and/or export a report, follow these steps:
IMPORTANT: To ensure that reports are most relevant and up-to-date, perform data collection
and complete the process immediately prior to generating or exporting a report. This saves an
up-to-date CSV data collection log file that you can use as the basis of your report (select the file
in step 1).
Reports pages
49
1.
2.
In the first field in the Specify Data Report file section, click the drop-down menu (
) button
on the right to list the available CSV data collection log files, and select the file you want to
view. To view a report based on the most recently-collected data, select the most recent log
file, as denoted by the file name.
If you want to export this file, select the desired export file format (XML or CSV) and click
Generate File.
Right click the file name to open or save the file, as shown in Figure 44 (page 50). If you
choose to generate an XML file, you can open the file in your browser. To export the file to a
specific destination, select Save target as... and indicate the location.
Figure 44 Generate or export file
3.
4.
5.
6.
If you want to view a graph of the data in the selected file, click Show Graph.
On the right side of the graph, select the counters you want included or excluded in the graph
(for convenience, use the Select/Unselect All check box to select or exclude all counters listed).
You can repeat this step to change the graph to reflect different counters. A key code is listed
to show what the colors in the graph represent.
To show a specific area of the graph, select the area in the Overview graph. The selected
area will be reflected in the larger graph on the left.
Click Generate File to create the report.
To compare data collection log files, follow these steps:
1. From the upper drop-down menu, select the first CSV file to compare. In Figure 43 (page 49),
the CpuPerfColl-12–20–12–16–08–47.csv file is selected.
2. From the lower drop-down menu, select the second CSV file to compare. In Figure 43
(page 49), the CpuPerfColl-12–20–12–16–22–42.csv file is selected.
3. Click Show Comparison Graph. In Figure 43 (page 49), graphs of both files are shown.
50
Using HP ESO
4.
Optionally, counters within each file to be compared can be filtered using the Select/Unselect
All check box on the right side of the graph, or by selecting individual counters to be included
in the comparison.
NOTE: The longer the data collection process is running, the more data will be stored in the CSV
(Comma Separated Values) files. When the amount of data collected is very large (exceeding
10MB, roughly), the ESO Workload and Performance History page may not be able to show the
entire graph. If this issue is encountered, use external applications such as Microsoft Excel to view
and graph the CSV files located in C:\Program Files\McPerfOpt\Data.
Save/Rollback SQL Configuration
Use this page to save the current system configuration to an XML file and retrieve it for future use.
Figure 45 (page 51) shows an example of the Save/Rollback SQL Configuration page.
Figure 45 Save/Rollback SQL Configuration page
The Save/Rollback SQL Configuration page displays the following values or controls:
•
Save Current Settings ⇒ Saves the current settings to an XML file. You can enter comments
and a description to make it easier to identify the saved settings in the future.
•
Restore Settings section ⇒ Retrieve, apply, or delete previously saved settings. To retrieve
settings, follow these steps:
1. Select the desired restoration point settings file by checking its box in the first column.
2. Click View Detail to display the contents of the selected restoration point settings file.
Figure 46 (page 52) shows an example showing a portion of the settings for a selected
restoration point. The Restore button, which becomes active when you select a single
restoration point settings file, allows you to restore the selected settings (next step). The
View Detail feature responds only if the selected restoration point settings differ from the
current settings. To view details of a restoration point settings file, you must select only
one file; do not select the Select All check box.
3. To apply the settings contained in the selected restoration file, click Restore.
Reports pages
51
Figure 46 Restoring selected settings
To delete saved restoration point settings, select the restoration point settings files and click Delete
to delete the selected files; you can select the Select All check box to delete all of the saved settings
files.
52
Using HP ESO
NOTE: With the current version of ESO, the Save/Rollback SQL Configuration feature only covers
the following parameters in the SQL Server page and the Network page:
SQL Server page
•
MaxWorkerThreads
•
Maximum Degree of Parallelism
•
Lightweight Pooling
•
Priority Boost
•
Minimum Server Memory (MB)
•
Maximum Server Memory (MB)
•
CheckPoint
•
Lock Pages in Memory
•
Flight Recorder
•
ResourceMonitoringEnabled
•
Random File Access
•
LowMemoryLimit
•
TotalMemoryLimit
•
CoordinatorQueryBalancingFactor
•
CoordinatorQueryBoostPriorityLevel
•
EnableRolapDistinctCountOnDataSource
Network page
•
RSS Status
•
Base RSS Processor
•
Max RSS Processors
The following parameters are not covered by the Save/Rollback SQL Configuration feature:
•
SQL Server — Xp_CmdShell
•
Database — Auto Create Statistics
•
Database — Auto Update Statistics
•
Database — Auto Update Statistics Async
•
Database (Database File) — AutoGrowth
•
CPU — CPU Affinity
•
SQL Server Startup — All trace flag status
•
Storage — User Write Cache Setting
•
Storage — Cache Power Protection
•
Network — NUMA Node Affinity
•
Network — Interrupt Affinity
•
Network — Port Affinity
•
Network — RSS Ring/Queue
Reports pages
53
Help pages
The Help pages display the HP ESO Online Help system. Available topics are identical in structure
and content to the HP ESO User Guide document. Use this page to find the information and help
you need to use HP ESO effectively.
Online help
Use this page as your entry point into HP ESO online help. Click the links in the table of contents
to find the desired information about using HP ESO. Figure 47 (page 54) shows the initial Online
Help page.
Figure 47 Online Help page
54
Using HP ESO
4 Support and other resources
Contacting HP
Before you contact HP
Be sure to have the following information available before you call or contact HP:
•
Technical support registration number (if applicable)
•
Product serial number
•
Product model name and number
•
Product identification number
•
Applicable error message
•
Add-on boards or hardware
•
Third-party hardware or software
•
Operating system type and revision level
HP contact information
For the name of the nearest HP authorized reseller:
•
See the Contact HP worldwide (in English) webpage:
http://www8.hp.com/us/en/hp-information/summary/ww-contact-us.html
For HP technical support:
•
In the United States, for contact options see the Contact HP/Customer Service webpage:
http://www8.hp.com/us/en/contact-hp/contact.html. To contact HP by phone:
◦
Phone:1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7
days a week. For continuous quality improvement, calls may be recorded or monitored.
◦
If you have purchased a Care Pack (service upgrade), call 1-800-633-3600. For more
information about Care Packs, see the following HP webpage:
http://www.hp.com/go/carepack
•
In other locations, see the Contact HP worldwide (in English) webpage:
http://welcome.hp.com/country/us/en/wwcontact_us.html
Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business webpage:
http://www.hp.com/united-states/subscribe/gateway/
After registering, you will receive email notification of product enhancements, new driver versions,
firmware updates, and other product resources.
New and changed information in this edition
This edition covers updates for the HP ESO 3.0 release, including new ESO 3.0 features and
changes. Illustrations have been updated to show revised windows and webpages. The new
features for HP ESO 3.0 are summarized in “New features in release 3.0” (page 7).
Contacting HP
55
Related information
The HP ESO release notes are available on the HP Business Support Center website from where
the HP ESO software is obtained.
The latest release of the HP ESO User Guide and other HP ProLiant DL980 documentation can be
found at the following HP Business Support Center webpage:
http://hp.com/go/proliant-DL980-docs
For information about HP ProLiant servers, see the following HP webpage:
http://www.hp.com/go/proliant
Typographic conventions
This document uses the following typographical conventions:
WARNING
A warning calls attention to important information that, if not understood
or followed, results in personal injury or nonrecoverable system problems.
56
CAUTION
A caution calls attention to important information that, if not understood
or followed, might result in data loss, data corruption, or damage to
hardware or software.
IMPORTANT
This alert provides essential information to explain a concept or to
complete a task.
NOTE
A note contains additional information to emphasize or supplement
important points of the main text.
KeyCap
The name of a keyboard key or graphical interface item (such as buttons,
tabs, and menu items).
Computer output
Text displayed by the computer.
User input
Commands and other text that you type.
Command
A command name or qualified command phrase.
Ctrl+x
A key sequence. A sequence such as Ctrl+x indicates that you must press
the key labeled Ctrl while you press another key or mouse button.
Support and other resources
5 Documentation feedback
HP is committed to providing documentation that meets your needs. To help us improve the
documentation, send any errors, suggestions, or comments to Documentation Feedback
(docsfeedback@hp.com). Include the document title and part number, version number, or the URL
when submitting your feedback.
57
Download PDF
Similar pages