5.6
Table Of Contents
- VMware vCenter Configuration Manager Installation Guide
- Contents
- About This Book
- Achieving a Successful VCM Installation
- Hardware Requirements for Collector Machines
- Software and Operating System Requirements for Collector Machines
- Preparing for Installation
- System Prerequisites to Install VCM
- Configure Resources to Install VCM on a Virtual Machine
- Secure Communications Certificates
- Single-Tier Server Installation
- Two-Tier Split Installation
- Three-Tier Split Installation
- Configuring a Three-Tier Split Installation Environment
- Installation Prerequisites for All Servers
- Configuring the VCM Database Server
- Configuring the Web Server
- Verify the Server Role Services on the Web Server
- Verify the IIS Server-Side Includes Role Service
- Verify the ISAPI Extensions
- Install the .NET Framework
- Verify the Authentication Settings
- Install SQL Server on the Web Server
- Install SQL Server 2008 Utilities
- Place the Web Server in the Internet Explorer Trusted Zone
- Configuring SSRS on the Web Server
- Configuring the VCM Collector
- Configuring Additional Components for a Three-Tier Environment
- Installing VCM
- Configuring SQL Server for VCM
- Upgrading or Migrating VCM
- Upgrading VCM and Components
- Upgrading Virtual Environments Collections
- Migrating VCM
- Prerequisites to Migrate VCM
- Migrate Only Your Database
- Replace Your Existing 32-Bit Environment with a Supported 64-bit Environment
- Migrate a 32-bit Environment Running VCM 5.3 or Earlier to VCM 5.6
- Migrate a 64-bit Environment Running VCM 5.3 or Earlier to VCM 5.6
- Migrate a Split Installation of VCM 5.3 or Earlier to a Single-Tier, Two-Tier...
- How to Recover Your Collector Machine if the Migration is not Successful
- Maintaining VCM After Installation
- Hardware and Operating System Requirements for VCM Managed Machines
- VCM Agent Support on Non-English Windows Platforms
- VCM Managed Machine Requirements
- Windows Custom Information Supports PowerShell 2.0
- Supported OS Provisioning Target Systems
- Software Provisioning Requirements
- UNIX and Linux Patch Assessment and Deployment Requirements
- Support for VMware Cloud Infrastructure
- vCenter Operations Manager Integration Features
- FIPS Requirements
- Agent Sizing Information
- Hardware and Software Requirements for the Operating System Provisioning Server
- Installing, Configuring, and Upgrading the OS Provisioning Server and Components
- Index
Configuring SQL Server for VCM
12
Configuring SQL Server for VCM
VCM relies heavily on its SQL databases for operation. You must update the default settings to optimize
SQL Server performance. These settings include the SQLServer database settings, processor settings, and
the Input/Output (I/O) configuration.
To ensure that VCM runs at peak performance and requires little operator intervention during its lifecycle,
set up a routine maintenance plan. See the VCM Administration Guide.
SQL Server Database Settings
Configure the database settings for VCM to optimize SQLServer performance.
Procedure
1. Click Start.
2. Select All Programs > Microsoft SQL Server 2008 R2 > SQL Server Management Studio.
3. Right-click the SQL instance that you installed and select Properties.
4. In the Select a page area, select Database Settings.
5. Configure the following settings.
n
Default index fill factor: Sets a percentage value for the amount of free space in each index page
when the page is rebuilt. Set the fill factor to 80% to keep 20% free space available in each index
page. This setting is part of the SQL maintenance plan wizard. If you configure the default fill factor
using this setting, keep free space in an index when you run a maintenance plan.
n
Recovery interval (minutes): Configures the approximate amount of time that SQL Server takes to
run the recovery process. Set the value to 5. The default setting is 0, which causes SQLServer to
adjust this value and base the values on the historical operation of the server. In large
environments, the recovery interval can affect the overall performance of VCM. Because VCM
constantly updates how it interacts with SQL Server to process activities whose intervals differ, such
as an inspection request and a compliance run, the server expends much time constantly adjusting
this value. By setting the recovery interval to 5 minutes, SQL Server no longer must tune this value.
6. Click OK to save the settings.
VMware, Inc.
85