HP IO Accelerator for BladeSystem c-Class Guide de l'utilisateur

Microsoft SQL Server Configuration Guide for HP IO Accelerators Part Number 647096-001 December 2010 (First Edition)

Testing IO Accelerator-powered SQL performance 10 o Physical Disk—Average Disk queue Length o Logical Disk—Avg. Disk sec/Read [Read Latency] o L

Architectural scenarios 11 Architectural scenarios Scenario 1: The entire database fits on the IO Accelerators 1. Place the data files on one IO Ac

Architectural scenarios 12 • Determine the maximum size of the tempdb file you need and then create each tempdb data file to be the same size. • T

Architectural scenarios 13 data for each year. In this scenario, you can keep the most recent data on IO Accelerators and keep older data on more tr

Acronyms and abbreviations 14 Acronyms and abbreviations CPU central processing unit DBCC database console commands IOPS input/output operations p

© Copyright 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties

Contents 3 Contents Installing and preparing the IO Accelerator for Microsoft Windows SQL Server ... 4 Initial setup

Installing and preparing the IO Accelerator for Microsoft Windows SQL Server 4 Installing and preparing the IO Accelerator for Microsoft Windows SQL

RAID options 5 RAID options RAID 0 RAID 0 offers the full capacity of the IO Accelerator without any disk-level redundancy. NOTE: Windows® Soft

High availability considerations 6 High availability considerations Database mirroring NOTE: Database mirroring requires Windows® SQL Server 20

High availability considerations 7 Third-party software is required to keep the data in sync between the different cluster nodes. HP recommends the

Backup considerations 8 Backup considerations General recommendations Backing up large SQL Server databases often takes a long time and ends up affe

Testing IO Accelerator-powered SQL performance 9 Testing IO Accelerator-powered SQL performance Methodology Generally, benchmarks such as SQLIO and