Professional Microsoft SQL Server 2008 Administration ppt

You’ll learn the various tools that are available to you with the 2008 release, as well as new features such as Performance Studio, Change Data Capture, Policy-based Management, and Quer

Wrox Professional guides are planned and written by working programmers to meet the real-world needs of programmers,

developers, and IT professionals Focused and relevant, they address the issues technology professionals face every day They

provide examples, practical solutions, and expert education in new technologies, all designed to help programmers do a better job

Recommended Computer Book Categories

Database Management General

ISBN: 978-0-470-24796-9

SQL Server 2008 represents a significant jump forward in scalability

and performance Database administrators — and developers as well —

will need to master new methods for effectively managing increasingly

large and complex SQL Server environments

This author team of SQL Server experts arms you with unique tips,

tricks, and workarounds, including managing and monitoring SQL

Server, automating administration, clustering, performance tuning,

handling backup and recovery, and more You’ll learn the various tools

that are available to you with the 2008 release, as well as new features

such as Performance Studio, Change Data Capture, Policy-based

Management, and Query Governor With a solid understanding of SQL

Server 2008, you’ll be able to confidently handle even the most difficult

SQL Server admin issues

What you will learn from this book

● Best practices for SQL Server 2008 installation

● Tips for troubleshooting and securing the database engine

● How to automate SQL Server

● Ways to index your database

● Methods for monitoring your SQL Server instance

● How to performance tune your SQL Server instance

Who this book is for

This book is for experienced database administrators who are

interested in learning best pratices for administering SQL Server 2008

Enhance Your Knowledge Advance Your Career

Professional SQL Server 2008 Reporting Services978-0-470-24201-8

This book teaches solutions architects, designers, and developers how to use Microsoft’s reporting platform to create reporting and business intelligence solutions

Professional Microsoft SQL Server 2008 Analysis Services978-0-470-24798-3

Professional Microsoft SQL Server 2008 Analysis Services shows readers how to

build data warehouses and multidimensional databases, query databases, and use Analysis Services and other components of SQL Server to provide end-to-end solutions

Professional Microsoft SQL Server 2008 Programming978-0-470-25702-9

This updated new edition of Wrox’s best-selling SQL Server book has been expanded

to include coverage of SQL Server 2008’s new datatypes, new indexing structures, manageability features, and advanced time-zone handling

Professional Microsoft SQL Server 2008 Administration978-0-470-24796-9

A how-to guide for experienced database administrators, this book is loaded with unique tips, tricks, and workarounds for handling the most difficult SQL Server administration issues The authors discuss data capture, performance studio, Query Governor, and new techniques for monitoring and policy management

Beginning Microsoft SQL Server 2008 Programming978-0-470-25701-2

This comprehensive introduction to SQL Server covers the fundamentals and moves on to discuss how to create and change tables, manage keys, write scripts, work with stored procedures, and much more

Beginning T-SQL with Microsoft SQL Server 2005 and 2008978-0-470-25703-6

Beginning T-SQL with Microsoft SQL Server 2005 and 2008 provides a comprehensive introduction to the T-SQL programming language, with

concrete examples showing how T-SQL works with both SQL Server 2005 and SQL Server 2008

Beginning Database Design Solutions978-0-470-38549-4

Beginning Database Design Solutions introduces IT professionals—both DBAs and database developers—to database design It explains what

databases are, their goals, and why proper design is necessary to achieve those goals It tells how to decide what should be in a database to

Get more out of

Wrox Online Library

Hundreds of our books are available online

through Books24x7.com

Wrox Blox

Download short informational pieces and

code to keep you up to date and out of

trouble!

Chapters on Demand

Purchase individual book chapters in pdf format

Join the Community

Sign up for our free monthly newsletter at newsletter.wrox.com

Browse

Ready for more Wrox? We have books and e-books available on NET, SQL Server, Java, XML, Visual Basic, C#/ C++, and much more!

Contact Us

We always like to get feedback from our readers Have a book idea?

Professional Microsoft ® SQL Server ® 2008 Administration

Introduction xxix

Chapter 1: SQL Server 2008 Architecture 1

Chapter 2: SQL Server 2008 Installation Best Practices 35

Chapter 3: Upgrading SQL Server 2008 Best Practices 63

Chapter 4: Managing and Troubleshooting the Database Engine 97

Chapter 5: Automating SQL Server 129

Chapter 6: Integration Services Administration and Performance Tuning 175

Chapter 7: Analysis Services Administration and Performance Tuning 207

Chapter 8: Administering the Development Features 237

Chapter 9: Securing the Database Engine 329

Chapter 10: Change Management 383

Chapter 11: Configuring the Server for Optimal Performance 413

Chapter 12: Optimizing SQL Server 2008 455

Chapter 13: Monitoring Your SQL Server 497

Chapter 14: Performance Tuning T-SQL 555

Chapter 15: Indexing Your Database 605

Chapter 16: Replication 653

Chapter 17: Database Mirroring 683

Chapter 18: Backup and Recovery 731

Chapter 19: SQL Server 2008 Log Shipping 779

Chapter 20: Clustering SQL Server 2008 807

Index 839

Administration

Administration

Brian Knight Ketan Patel Wayne Snyder Ross LoForte Steven Wort

Wiley Publishing, Inc.

Professional Microsoft® SQL Server® 2008 Administration

Copyright © 2009 by Wiley Publishing, Inc., Indianapolis, Indiana

Published simultaneously in Canada

ISBN: 978-0-470-24796-9

Manufactured in the United States of America

10 9 8 7 6 5 4 3 2 1

Library of Congress Cataloging-in-Publication Data

Microsoft SQL server 2008 administration / Brian Knight [et al.].

No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any

means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections

107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or

authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood

Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600 Requests to the Publisher for permission should be

addressed to the Legal Department, Wiley Publishing, Inc., 10475 Crosspoint Blvd., Indianapolis, IN 46256, (317)

572-3447, fax (317) 572-4355, or online atwww.wiley.com/go/permissions.

with respect to the accuracy or completeness of the contents of this work and specifically disclaim all warranties,

including without limitation warranties of fitness for a particular purpose No warranty may be created or extended

by sales or promotional materials The advice and strategies contained herein may not be suitable for every

situation This work is sold with the understanding that the publisher is not engaged in rendering legal, accounting,

or other professional services If professional assistance is required, the services of a competent professional person

should be sought Neither the publisher nor the author shall be liable for damages arising herefrom The fact that an

organization or Website is referred to in this work as a citation and/or a potential source of further information

does not mean that the author or the publisher endorses the information the organization or Website may provide

or recommendations it may make Further, readers should be aware that Internet Websites listed in this work may

have changed or disappeared between when this work was written and when it is read.

For general information on our other products and services please contact our Customer Care Department within the

United States at (800) 762-2974, outside the United States at (317) 572-3993 or fax (317) 572-4002.

are trademarks or registered trademarks of John Wiley & Sons, Inc and/or its affiliates, in the United States and other

countries, and may not be used without written permission Microsoft and SharePoint are registered trademarks of

Microsoft Corporation in the United States and/or other countries All other trademarks are the property of their

respective owners Wiley Publishing, Inc., is not associated with any product or vendor mentioned in this book.

Wiley also publishes its books in a variety of electronic formats Some content that appears in print may not be

available in electronic books.

About the Authors

Brian Knight, SQL Server MVP, MCSE, MCDBA, is the co-founder of SQLServerCentral.com and startTV.com Brian is a principal consultant and owner of Pragmatic Works He runs the local SQL

Jump-Server users group (JSSUG) in Jacksonville, Florida, and was on the Board of Directors of the

Profes-sional Association for SQL Server (PASS) Brian is a contributing columnist for SQL Server Standard,

maintains a regular column for the database website SQLServerCentral.com, and does regular webcasts

at Jumpstart TV He is the author of nine SQL Server books Brian is a speaker at numerous

confer-ences, including PASS, SQL Connections, and TechEd, and many code camps His blog can be found at

www.pragmaticworks.com Brian spends weekends practicing to be an amateur surgeon and proceeds

from this book will help pay for the mobile CAT scan for his van

Ketan Patel, B.E., electronics engineering, MCSE, MCDBA, is a senior development manager for the

Business Intelligence Center of Excellence group at Microsoft He has worked with SQL Server and otherMicrosoft technologies for nearly nine years Ketan has also spoken at TechEd He spends his spare timewith his family and friends, playing cricket and watching NFL

Wayne Snyderis recognized worldwide as a SQL Server expert and Microsoft Most Valued Professional(MVP), with over 25 years of experience in project management, database administration, software

design, performance measurement, and capacity planning He is a popular consultant, trainer, writer,

and speaker, and produces a series of Web-based seminars on SQL Server 2005 Wayne has edited

many SQL Server books, has SQL Training CDs with Learnkey, is president of PASS, the Professional

Association for SQL Server (www.sqlpass.org), plays keyboard for a cover band named

SoundBar-rier (www.soundbarrierband.com), and is a managing consultant for Mariner, a Business Intelligence

Company (www.mariner-usa.com)

Ross LoForteis a technical architect at the Microsoft Technology Center Chicago, focused on MicrosoftSQL Server solutions Ross has more than 16 years of experience in business development, project man-agement, and designing SQL architecture solutions For the past eight years, Ross has been working withthe Microsoft Technology Centers, and has led architecture design and proof-of-concept engagements

for Microsoft’s largest and most strategic customers to design enterprise, mission-critical SQL Server

solutions Ross is a SQL Server instructor at DePaul University in Chicago, and regularly presents at

TechEd, SQL PASS, Gartner, TDWI, and other conferences A published author, he has been active withthe Professional Association for SQL Server, the Chicago SQL Server Users Group, and the SQL Server

community for many years

Steven Worthas been working with SQL Server for the past 14 years He spent much of that time working

as a freelance application developer and database architect building VB and Web applications on SQL

Server for many of London’s largest financial institutions He moved to the United States nine years ago,joining Microsoft over seven years ago After three years working in PSS on the SIE team, he moved over

to the SQL Server Product group, spending a year working on SQL Server scalability, followed by a yearworking with the SQL Playback team Two years ago Steven moved to the Windows division, where hestarted work on the SQL Server side of the Watson system When he is not involved with technology,

Steven can be found doing something active somewhere outdoors in the Pacific Northwest

Geoff Hiten, a Microsoft MVP, is a senior SQL Server consultant based in Atlanta Geoff began

working with SQL Server in 1992 with version 4.2 and has used every version since He specializes in

high-availability and high-performance SQL systems Recent projects include: system upgrades, SQL

Server platform migrations, performance tuning, custom reporting solutions, and database strategy

implementations Geoff is currently on the leadership team of the Atlanta area Microsoft Database Forum

Users group (AtlantaMDF) and can be found lurking in the halls at PASS (Professional Association

for SQL Server) Community Summit events In addition, Geoff has been a Subject Matter Expert for

Microsoft Training Curriculum materials and has authored articles, white papers, and podcasts on SQL

Server

K Brian Kelley(MCSE, Security+, CISA) is a systems and security architect for AgFirst Farm Credit

Bank At AgFirst he provides infrastructure and security guidance with respect to Windows-based

tech-nologies including Active Directory, Internet Information Server, and Microsoft SQL Server Brian, author

of Start to Finish Guide to SQL Server Performance Monitoring and contributing author for How to Cheat at

Securing SQL Server 2005, is a regular columnist and blogger at SQLServerCentral.com focusing primarily

on SQL Server security He is also a frequent contributor for SQL Server Standard Magazine Brian is a

member of the Professional Association of SQL Server (PASS) and the Information Systems Audit and

Control Association (ISACA) He is also active in the Midlands PASS chapter, an official PASS chapter

for South Carolina

Robert Swanson

As always, I must thank my wife and best friend for supporting me for the past 10 years of marriage

I’ve been fortunate to have found a woman who doesn’t fall asleep immediately when copyediting my

technical writing Thanks to my three children, Colton, Liam, and Camille, for allowing their daddy

to be distracted sometimes with this book when they wanted to play Thanks also to all the wonderful

co-authors, who truly made this book possible Once again, I must thank the Pepsi-Cola Company for

inventing Mountain Dew, which drove the late night writing — Brian Knight

I would like to thank my parents, Thakorbhai and Induben, for their unwavering and selfless support andinspiration in my life, and my wife, Sweety, for her invaluable support and understanding I would like toacknowledge Brian Knight, the lead author, for providing me with a great opportunity to co-author thisbook I would also like to acknowledge Sara Shlaer, the development editor, and John Mueller, technicaleditor — without them this book would not exist or contain the level of depth that it has Last but not theleast, I want to thank B J Moore and Jim Walch, both general managers at Microsoft, for their invaluable

support and encouragement — Ketan Patel

Thank-you to my loving wife, Vickie, whose generosity and support make my life better each day

— Wayne Snyder

I’d like to thank my wife, Anna, and my daughter, Jennifer, for their support while writing this book

Additionally, I’d like to thank Adam Hecktman and Tony Surma for their support, and for making the

Microsoft Technology Center Chicago a great facility to learn and experience — Ross LoForte

I have to start by thanking my wife, Tracy, and two daughters, Eleanor and Caitlin, for putting up with

me over the past few months of writing They have been infinitely patient and understanding while I

have spent many long hours working I must also thank everyone in the SQL Product Group who has

helped me with information about SQL Server 2008 Finally, I would like to thank everyone at Wrox

Press for their help with this work over the past months — Steven Wort

I would like to thank my wife Cheryl for being my other, better half, and my children; Victoria,

Alexan-dra, and Katherine, who challenge me to do better simply by being who they are — Geoff Hiten

Thanks to Kimberly, my beautiful bride and my children, James, Paul, and Faye I love you all very much.Thanks also to Brian Knight for opening the door and to Mark Melichar for encouraging me to seize the

opportunity You guys have been great mentors and I can’t thank you enough — K Brian Kelly

Production DBA 1Development DBA 2Business Intelligence DBA 3Hybrid DBA 3New Things You Need to Learn 4

Transaction Log and Database Files 5SQL Native Client 6System Databases 7Schemas 9Synonyms 9Dynamic Management Views 10SQL Server 2008 Data Types 10

Compact (32-bit only) 17SQL Express (32-bit only) 17Workgroup Edition (32-bit and 64-bit) 17Web Edition (32-bit and 64-bit) 17Standard Edition (32-bit and 64-bit) 17Enterprise, Evaluation, and Developer Editions (32-bit and 64-bit) 17Operating System 18Maximum Capacity of SQL Server 18Database Features By Edition 19Licensing 31

Hardware Options 36Software and Install Options 40

Where Are the Sample Databases? 50

SQL Server Configuration Manager 53

SQL Server Management Studio 53

tempdb 54

Back It Up 56

Uninstalling Reporting Services 57

Uninstalling Analysis Services 58

Uninstalling the SQL Server Database Engine 58

Installing Client Tools from a Network Share 59

Admin Tools Not Installed by Default on Remote Cluster Nodes 60

Minimum Configuration Warning 60

Risk Mitigation — The Microsoft Contribution 64

Independent Software Vendors and SQL Community Contributions 65

SQL Server Upgrade Advisor 69

Installing the SQL Server 2008 Upgrade Advisor 69

Using the Upgrade Advisor 70

Scripting the Upgrade Advisor 72

Resolving Upgrade Issues 73

SQL Server 2008 Upgrade Assistant 75

Unsupported and Discontinued Features 77

SQL Server 2008 Deprecated Database Features 78

SQL Server Component Considerations 79

Upgrading Full-Text Catalog to SQL Server 2008 79Upgrading Reporting Services 80Upgrading Analysis Services 80Upgrading DTS to SQL Server 2008 Integration Services (SSIS) 81Log Shipping 88Failover Clustering and Data Mirroring 88Upgrading to 64-bit 88

Poor Query Performance After Upgrade 89Updating Usage Counters 90SQL Server Configuration Manager 91Policy-Based Management 91

Reports 106Configuring SQL Server 108Filtering Objects 112Error Logs 113Activity Monitor 114Monitoring Processes in T-SQL 118

SQLDumper.exe 124SQLDiag.exe 125

Configuring SQL Server Agent 156

Database Mail 160

Multiserver Administration 166

Integration Services Uses 176

The Four Main Parts of Integration Services 177

Project Management and Change Control 179

An Overview of the Integration Services Service 179

Configuration 180

Event Logs 185

Monitoring Activity 187

An Overview of Integration Services Packages 187

Creating Packages 188

Management 191

Deployment 194

Execution and Scheduling 199

An Overview of Integration Services Security 203

Unified Dimensional Model Components 208

Analysis Services Architectural Components 209

Required Services 212

Analysis Services Scripting Language 212

Deploying Analysis Services Databases 214

Processing Analysis Services Objects 217

Backing Up and Restoring Analysis Services Databases 219

Synchronizing Analysis Services Databases 222

Analysis Services Performance Monitoring and Tuning 223

Monitoring Analysis Services Events Using SQL Profiler 223Creating Traces for Replay 224Using Flight Recorder for After-the-Fact Analysis 226

Storage Modes 227Partition Configuration 227Designing Aggregations 228

Server Role 233Database Role 233Database Role Permissions 234

Transport Security 267Routing 271Dialog Security 275

Setting Conversation Priorities 279Reviewing Conversation Priorities 288

Installing Service Broker Application 289Setting Permission on Service Broker Objects 290Managing Service Broker Queues 292Poison Message Handling 293Moving Service Broker Applications 295Copying Service Broker Applications 296Replacing Expired Certificates 297Troubleshooting Service Broker Applications 297Performance Tuning Service Broker 307

SQL Server As NET Runtime Host 308Application Domains 309T-SQL versus CLR 310Extended Stored Procedures versus CLR 310

Enabling CLR Integration 311

Creating the CLR Assembly 312

Deploying the Assembly 315

The Principle of Least Privilege 329

The CIA Triad 330

Defense in Depth 331

New Security Features in SQL Server 2008 332

Operating System Security 333

Operating System Security and SQL Server 337

Typical Endpoint Configuration 342

Other Endpoints 344

Windows Authentication Changes in SQL Server 2008 344

Changing the Schema Owner 363

INFORMATION_SCHEMA and sys Schemas 364

Setting Up an Encryption Methodology 370

Encrypting the Data 372

Creating a Helper Function Example 374Column-Level Permissions 374Transparent Data Encryption (TDE) 375Extensible Key Management (EKM) 377

Creating an Audit 377Creating and Enabling a Server Audit Specification 378Creating and Enabling a Database Audit Specification 380

Creating a Connection 384Creating a Project Query 385

Policy-Based Management Overview 386Policy-Based Management Step By Step 387Scripting Policy-Based Management 392Policy-Based Management Implementation 394DDL Trigger Syntax 397Database Triggers 397Server Triggers 401

Scripting Overview 403Executing sqlcmd from the Command Prompt 403Executing sqlcmd from Management Studio 405

Data Dude 408PowerShell 408Version Tables 410

The Performance Tuning Cycle 414Defining Good Performance 415Focus on What’s Most Important 415

Users 417SQL Statements 417

Data 417

Robust Schema 417

Windows Server System Reference Architecture 421

Windows Server Catalog 421

Physical Address Space 429

Virtual Memory Manager 429

The Page File 430

Page Faults 430

Virtual Address Space 431

32-Bit System Memory Configuration 432

Designing a Storage System 441

Large Storage System Considerations: SAN Systems 445

The Silent Killer: I/O Problems 456

SQL Server I/O Process Model 457Database File Placement 457tempdb Considerations 458

Why Consider Partitioning? 461Implementing Partitioning 462Creating a Partition Function 463Creating Filegroups 464Creating a Partition Scheme 464Creating Tables and Indexes 465

Row Compression 470Page Compression 471Estimating Space Savings 473Monitoring Data Compression 475Data Compression Considerations 475

Tuning SQL Server Memory 476Windows 2008 Hot-Add CPU 479Configuring SQL Server 2008 for Dynamic Memory on an X86 Platform 47964-bit Versions of SQL Server 2008 482Resource Governor 482

Data Locality 488Cache Coherency 489Affinity Mask 489Max Degree of Parallelism (MAXDOP) 492Affinity I/O Mask 492Max Server Memory 493Index Creation Memory Option 494Minimum Memory per Query 494

Determining Your Monitoring Objectives 498Establishing a Baseline 498Comparing Current Metrics to the Baseline 499

What’s New in Monitoring for SQL Server 2008 499

Data Collection 500

SQL Server Extended Events 500

CPU Resource Counters 502

Isolating Processor Bottlenecks 503

SQL Server Extended Event Notifications 531

What’s Going on Inside SQL Server 540

Viewing the Locking Information 543

Viewing Blocking Information 543

Index Usage in a Database 544

View Queries Waiting for Memory Grants 545

Connected User Information 546

Filegroup Free Space 546

Query Plan and Query Text for Currently Running Queries 547

Memory Usage 547

Monitoring the SQL Server Error Log 548

Monitoring the Windows Event Logs 548

System Data Collection Sets 549

Viewing Data Collected By the System Data Collection Sets 549

Creating Your Own Data Collection Set 551

Examining the Data You Collected 553

Compilation 559

Tools and Commands for Recompilation Scenarios 563

Parser and Algebrizer 564

Optimization 565

Tuning Process 570

Database I/O Information 570Working with the Query Plan 571Join Algorithms 579Index Access Methods 582Data Modification Query Plan 595Query Processing Enhancements on Partitioned Tables and Indexes 600Gathering Query Plans for Analysis with SQL Trace 602

What’s New for Indexes in SQL Server 2008 605Index Features from SQL Server 2005 606

Why Use Partitioned Tables and Indexes? 610Prerequisites for Partitioning 611Creating Partitioned Tables 611

Monitoring Index Fragmentation 626Cleaning Up Indexes 628

Using the DTA to Tune Individual Queries 630Too Many Indexes? 649Tuning a Workload 651

Replication Types 654Replication Components 655Replication Enhancements in SQL Server 2008 656

Single Publisher, One or More Subscribers 657Multiple Publishers, Single Subscriber 658Multiple Publishers Also Subscribing 658Updating Subscriber 660Peer-to-peer 660

Implementing Replication 661

The Setup 662

Setting Up Distribution 663

Implementing Snapshot Replication 666

Implementing Transactional and Merge Replication 674

Operating Modes of Database Mirroring 685

Database Mirroring Example 687

Database Mirroring and SQL Server 2008 Editions 697

Database Mirroring Catalog Views 698

Database Mirroring Role Change 700

Database Availability Scenarios 706

Monitoring Using System Monitor 709

Monitoring Using Database Mirroring Monitor 711

Setting Thresholds on Counters and Sending Alerts 714

Monitoring Using SQL Profiler 716

Troubleshooting Setup Errors 716

Troubleshooting Runtime Errors 717

Automatic Page Repair 718

Hardware, Software, and Server Configuration 719

Database Availability During Planned Downtime 720

SQL Job Configuration on the Mirror 722

Database TRUSTWORTHY Bit on the Mirror 722

Client Redirection to the Mirror 722

Database Mirroring and Clustering 724

Database Mirroring and Transactional Replication 725

Database Mirroring and Log Shipping 725

Mirroring Event Listener Setup 725

Backup/Recovery Plan 734Maintaining the Plan 738

How Backup Works 739Backup Compression 742How Restore Works 743Comparing Recovery Models 744Choosing a Model 745Switching Recovery Models 746Verifying the Backup Images 747Backing Up History Tables 749Permissions Required for Backup and Restore 750Backing Up System Databases 750Full-text Backup 751

Recoverability Requirements 752Data Usage Patterns 753Maintenance Time Window 753Other High-Availability Solutions 755

Using SQL Server 2008 Management Studio 755Database Maintenance Plans 760Using Transact-SQL Backup Commands 762

Restore Process 765SQL Server Management Studio Restore 769

Log Shipping to Create a Warm Standby Server 780

Log Shipping As a Disaster Recovery Solution 780

Log Shipping As a Report Database Solution 781

Deploying with Management Studio 786

Deploying with T-SQL Commands 790

Monitoring with Management Studio 792

Monitoring with Stored Procedures 793

Troubleshooting Approach 793

Synchronizing Dependencies 794

Switching Roles from the Primary to Secondary Servers 796

Switching Between Primary and Secondary Roles 798

Redirecting Clients to Connect to the Secondary Server 799

Database Backup Plan 800

SQL Server 2008 Data Mirroring 801Windows Failover Clustering 801SQL Server 2008 Replication 801

Removing Log Shipping with Management Studio 802Removing Log Shipping with T-SQL Commands 802

Minimum Downtime Approach 803With Downtime Approach 804Deploy Log Shipping Approach 804

What Clustering Can Do 808What Clustering Cannot Do 809Choosing SQL Server 2008 Clustering for the Right Reasons 810Alternatives to Clustering 810

How Clustering Works 812Clustering Options 814

Don’t Upgrade 817Upgrading Your SQL Server 2008 Cluster In-Place 817Rebuilding Your Cluster from Scratch 817Backout Plan 819Which Upgrade Option Is Best? 819

Preparing the Infrastructure 820Preparing the Hardware 821

Before Installing Windows 2008 Clustering 823Installing Windows Server 2008 Clustering 824Configuring Windows Server 2008 for Clustering 827

Clustering SQL Server 2008 828

Clustering SQL Server 828

Installing the Service Pack and Hot Fixes 831

Test, Test, and Test Again 831

How to Approach Clustering Troubleshooting 834

Doing It Right the First Time 835

I n t r o d u c t i o n

SQL Server 2008 represents a sizable jump forward in scalability, performance, and usability for the

DBA, developer, and business intelligence (BI) developer It is no longer unheard of to have 20-terabytedatabases running on a SQL Server SQL Server administration used to just be the job of a database

administrator (DBA), but as SQL Server proliferates throughout smaller companies, many developers

have begun to act as administrators as well Additionally, some of the new features in SQL Server are

more developer-centric, and poor configuration of these features can result in poor performance SQL

Server now enables you to manage the policies on hundreds of SQL Servers in your environment as if

you were managing a single instance We’ve provided a comprehensive, tutorial-based book to get youover the learning curve of how to configure and administer SQL Server 2008

Who This Book Is For

Whether you’re an administrator or developer using SQL Server, you can’t avoid wearing a DBA hat atsome point Developers often have SQL Server on their own workstations and must provide guidance tothe administrator about how they’d like the production configured Oftentimes, they’re responsible for

creating the database tables and indexes Administrators or DBAs support the production servers and

often inherit the database from the developer

This book is intended for developers, DBAs, and casual users who hope to administer or may already

be administering a SQL Server 2008 system and its business intelligence features, such as Integration

Services This book is a professional book, meaning the authors assume that you know the basics about

how to query a SQL Server and have some rudimentary concepts of SQL Server already For example,

this book does not show you how to create a database or walk you through the installation of SQL Serverusing the wizard Instead, the author of the installation chapter may provide insight into how to use

some of the more advanced concepts of the installation Although this book does not cover how to query

a SQL Server database, it does cover how to tune the queries you’ve already written

How This Book Is Str uctured

The first ten chapters of the book are about administering the various areas of SQL Server, including thedeveloper and business intelligence features Chapter 1 briefly covers the architecture of SQL Server andthe changing role of the DBA Chapters 2 and 3 dive into best practices on installing and upgrading to

SQL Server 2008 Managing your SQL Server database instance is talked about in Chapter 4 This chapteralso describes some of the hidden tools you may not even know you have

Once you know how to manage your SQL Server, you can learn in Chapter 5 how to automate many ofthe redundant monitoring and maintenance tasks This chapter also discusses best practices on config-

uring SQL Server Agent Chapters 6 and 7 cover how to properly administer and automate many tasksinside of the Microsoft business intelligence products, such as Integration Services and Analysis Services

Developers will find that Chapter 8 is very useful, as it covers how to administer the development

fea-tures, such as SQL CLR Chapter 9 explains how to secure your SQL Server from many common threats

and how to create logins and users Chapter 10 covers how to create a SQL Server project and do proper

change management in promoting your scripts through the various environments It also covers the

Policy-Based Management framework in SQL Server

Chapters 11 through 15 make up the performance tuning part of the book Chapter 11 discusses how to

choose the right hardware configuration for your SQL Server in order to achieve optimal performance

After the hardware and operating system is configured, Chapter 12 shows you how to optimize your SQL

Server instance for the best performance Chapter 13 describes how to monitor your SQL Server instance

for problematic issues such as blocking and locking Chapters 14 and 15 discuss how to optimize the

T-SQL that accesses your tables and then how to index your tables appropriately

Chapters 16 through 20 consist of the high-availability chapters of the book Chapter 16 covers how to

use the various forms of replication, while database mirroring is covered in Chapter 17 Classic issues

and best practices with backing up and recovering your database are discussed in Chapter 18 Chapter 19

dives deeply into the role of log shipping in your high-availability strategy, and Chapter 20 presents a

step-by-step guide to clustering your SQL Server and Windows 2008 server

This edition of the book covers all the same great information we covered in the last book, and we’ve

added loads of new content for SQL Server 2008, which adds numerous new features to improve the

DBA’s life In short, the new version of SQL Server focuses on improving your efficiency, the scale of your

server, and the performance of your environment, so you can do more in much less time, and with fewer

resources and people This means you can manage many servers at one time using Policy-Based

Manage-ment, scale your I/O load using compression, and collect valuable information about your environment

using data collectors, to name just a few key new features

What You Need to Use This Book

To follow the examples in this book, you will need to have SQL Server 2008 installed If you wish to

learn how to administer the business intelligence features, you need to have Analysis Services and

the Integration Services components installed You need a machine that can support the minimum

hardware requirements to run SQL Server 2008; and you also need theAdventureWorks2008and

AdventureWorksDW2008databases installed Instructions for accessing these databases can be found in

the ReadMe file on this book’s Web site

Some features in this book (especially in the high-availability part) require the Enterprise or Developer

Edition of SQL Server If you do not have this edition, you will still be able to follow through some of the

examples in the chapter with Standard Edition

Conventions

To help you get the most from the text and keep track of what’s happening, we’ve used a number of

conventions throughout the book

Boxes like this one hold important, not-to-be forgotten information that is directly

relevant to the surrounding text.

Tips, hints, tricks, and asides to the current discussion are offset and placed in italics like this.

As for styles in the text:

❑ We highlight new terms and important words when we introduce them.

❑ We show keyboard strokes like this: Ctrl+A

❑ We show file names, URLs, and code within the text like so:persistence.properties

❑ We present code in two different ways:

In code examples we highlight new and important code with a gray background

The gray highlighting is not used for code that’s less important in the present

context, or has been shown before; that code appears like this

Source Code

As you work through the examples in this book, you may choose either to type in all the code manually or

to use the source code files that accompany the book All of the source code used in this book is availablefor download atwww.wrox.com Once at the site, simply locate the book’s title (either by using the Searchbox or by using one of the title lists) and click the Download Code link on the book’s detail page to obtainall the source code for the book

Because many books have similar titles, you may find it easiest to search by ISBN; this book’s ISBN is

978-0-470-24796-9.

Once you download the code, just decompress it with your favorite compression tool Alternately, you

can go to the main Wrox code download page atwww.wrox.com/dynamic/books/download.aspxto seethe code available for this book and all other Wrox books

Errata

We make every effort to ensure that there are no errors in the text or in the code However, no one is

perfect, and mistakes do occur If you find an error in one of our books, such as a spelling mistake or a

faulty piece of code, we would be very grateful for your feedback By sending in errata, you may save

another reader hours of frustration and at the same time you will be helping us provide even higher

quality information

To find the errata page for this book, go towww.wrox.comand locate the title using the Search box or one

of the title lists Then, on the book details page, click the Book Errata link On this page you can view all

errata that has been submitted for this book and posted by Wrox editors A complete book list, including

links to each book’s errata, is also available atwww.wrox.com/misc-pages/booklist.shtml

If you don’t spot ‘‘your’’ error on the Book Errata page, go to www.wrox.com/contact/

techsupport.shtmland complete the form there to send us the error you have found We’ll

check the information and, if appropriate, post a message to the book’s errata page and fix the problem

in subsequent editions of the book

p2p.wrox.com

For author and peer discussion, join the P2P forums atp2p.wrox.com The forums are a Web-based

system for you to post messages relating to Wrox books and related technologies and interact with other

readers and technology users The forums offer a subscription feature to e-mail you topics of interest of

your choosing when new posts are made to the forums Wrox authors, editors, other industry experts,

and your fellow readers are present on these forums

Athttp://p2p.wrox.comyou will find a number of different forums that will help you not only as you

read this book, but also as you develop your own applications To join the forums, just follow these steps:

1. Go top2p.wrox.comand click the Register link

2. Read the terms of use and click Agree.

3. Complete the required information to join as well as any optional information you wish to

provide and click Submit

4. You will receive an e-mail with information describing how to verify your account and

com-plete the joining process

You can read messages in the forums without joining P2P but in order to post your own messages, you

must join.

Once you join, you can post new messages and respond to messages other users post You can read

messages at any time on the Web If you would like to have new messages from a particular forum

e-mailed to you, click the Subscribe to this Forum icon by the forum name in the forum listing

For more information about how to use the Wrox P2P, be sure to read the P2P FAQs for answers to

questions about how the forum software works as well as many common questions specific to P2P and

Wrox books To read the FAQs, click the FAQ link on any P2P page

SQL Ser ver 2008

Architecture

The days of SQL Server being merely a departmental database are long gone SQL Server can now

easily scale to databases dozens of terabytes in size (For details see the results of the Winter survey

atwww.microsoft.com/sql/prodinfo/compare/wintercorp-survey.mspx.) In this chapter, we lay

some of the groundwork that will be used throughout the book We first discuss how the role of the

database administrator (DBA) has changed since some of the earlier releases of SQL Server, and then

quickly jump into architecture and tools available to you as an administrator This chapter is not a

deep dive into the architecture but it provides enough information to give you an understanding of

how SQL Server operates

The Expanding Role of a DBA

The role of the database administrator has been changing slowly over the past few versions of the

SQL Server product Beginning with SQL Server 2005, this slow transition of the DBA role has

been accelerated immensely Traditionally, a DBA would fit into one of two roles: development or

administration It’s much tougher to draw a line now between DBA roles in SQL Server 2008 In

addition, the new role of Business Intelligence DBA is on the rise As lines blur and morph, DBAs

have to quickly prepare themselves to take on different roles If you don’t position yourself to be

more versatile, you may be destined for a career of watching SQL Server alerts and

backups

Production DBA

Production DBAs fall into the traditional role of a DBA They are a company’s insurance policy

that the production database won’t go down If the database does go down, the company cashes

in its insurance policy in exchange for a recovered database The Production DBA also ensures that

the server is performing optimally, and he or she promotes database changes from development

to quality assurance (QA) to production Other tasks performed by a Production DBA include the

following:

❑ Install SQL Server instances and service packs

❑ Monitor performance problems

❑ Install scripts from development

❑ Create baselines of performance metrics

❑ Configure the SQL Server optimally

❑ Configure/implement high availability plans

❑ Create\implement disaster recovery and scalability plans

❑ Ensure that backups have been run

Since the release of SQL Server 2000, there has been a trend away from full-time Production DBAs,

and the role has merged with that of the Development DBA The trend may have slowed, though, with

laws such as Sarbanes-Oxley, which require a separation of power between the person developing the

change and the person implementing the change In a large organization, a Production DBA may fall into

the operations department, which would consist of the network administrators and Windows-support

administrators Placing a Production DBA in a development group removes the separation of power that

may be needed for some regulatory reasons It may create an environment where ‘‘rush’’ changes are

immediately put into production, without proper inspection and auditing

Development DBA

Development DBAs also play a very traditional role in an organization They wear more of a developer’s

hat and are the development staff’s database experts and representatives This administrator ensures that

all stored procedures are optimally written and that the database is modeled correctly, both physically

and logically He or she also may be the person who writes the migration processes to upgrade the

database from one release to the next The Development DBA typically does not receive calls at 2:00 a.m

Other Development DBA tasks may be as follows:

❑ Model an application database

❑ Create stored procedures

❑ Develop the change scripts that go to the Production DBA

❑ Performance-tune queries and stored procedures

❑ Create data migration plans and scripts

❑ Serve as an escalation point for the Production DBA

The Development DBA typically would report to the development group He or she would receive

requests from a business analyst or another developer In a traditional sense, Development DBAs should

never have modification access to a production database They should, however, have read-only access

to the production database to debug in a time of escalation

Business Intelligence DBA

The Business Intelligence (BI) DBA is a new role that has evolved due to the increased capabilities of SQLServer In SQL Server 2005, BI grew to be an incredibly important feature set that many businesses couldnot live without The BI DBA is an expert at these features

BI DBAs may have specializations, just like normal SQL DBAs A Production BI DBA will perform the

same functions as the Production DBA: installs, service packs, deployments, high availability,

perfor-mance tuning, and backups The only difference is that the Production BI DBA will be paying closer

attention to SQL Server Analysis Services (SSAS), SQL Server Integration Services (SSIS), SQL Server

Reporting Services (SSRS), and perhaps Proclarity, Business Scorecard Manager, and Performance PointServers

Development BI DBAs specialize in the best practices, optimization, and use of the BI toolset In a smallorganization, he or she may create your SSIS packages to perform Extract Transform and Load (ETL) pro-cesses or reports for users In a large organization, developers create the SSIS packages and SSRS reports.The Development BI DBA is consulted regarding the physical implementation of the SSIS packages, andAnalysis Services (SSAS) cubes Development BI DBAs may be responsible for the following types of

functions:

❑ Model\consult regardingAnalysis Services cubes and solutions

❑ Create reports using Reporting Services

❑ Create\consult around ETL using Integration Services

❑ Develop deployment packages that will be sent to the Production DBA

Organizationally, the BI DBA most often reports to the development group In some cases, Analysis

Services experts may report to the analyst group or the project management office In some small zations, the BI DBA may report directly to an executive such as a CFO

organi-Hybrid DBA

The most exciting role for a DBA is a hybrid of all the roles just mentioned This Hybrid DBA is very

typical with smaller organizations but is becoming popular with larger organizations as well An zation with high turnover may want to spread its investment over many Hybrid DBAs instead of relying

organi-on specialized roles

Organizationally, you may see Hybrid DBAs reporting directly to the product organization or to a

specialized DBA group No matter where these DBAs report, each typically has a slate of products

that he or she supports, performing every DBA function for that product Organizations that rely on

Hybrid DBAs should have adequate backup personnel to reduce the organization’s risk if a Hybrid

DBA leaves the company Also, this DBA should never install his or her own changes into production

Ideally, for regulatory reasons and for stability, the DBA’s backup DBA should install the change into

production That way, you can ensure that the DBA who installed the script didn’t make ad hoc changes

in order to make the change work We cover much more about this change-management process in

Chapter 10

The only role of a Hybrid DBA that’s questionable is development of stored procedures In most

organi-zations where we see this role, the Hybrid DBA does not develop stored procedures Instead, he or she

creates difficult stored procedures or tunes the ones causing issues The developer working on the

appli-cation develops his or her own stored procedures and then provides them to the Hybrid DBA to package

and proof The main reason for this is that the DBA is too taxed for time, working on other functions of

the database

New Things You Need to Learn

The best of us continue to learn new skills and keep up with the changing face of software It is the

busi-ness we are in We must continue to grow and learn or risk becoming obsolete Each new release of SQL

Server since 7.0 has required DBAs to know more things that were traditional concerns of developers As

Microsoft puts more and more on the SQL Server CD, and integrates SQL Server with other development

environments, programs, and tools, the breadth of our skills must also grow Here are some reminders

of items that warrant your attention:

❑ Resource Governor allows you to manage workload by setting resource limits New in SQL

Server 2008, knowledge of this feature is a must for DBAs

❑ Certificates and Kerberos have been used in SQL Server since SQL 2005 While you do

not need to be an expert, you must spend some time getting acquainted with how these

things work Kerberos will become especially important if your site uses Reporting Services

(SSRS) and your Reporting Services database is on a separate server than Reporting Services

Web Service

❑ CLR Integration enables you to use NET programming in your stored procedures, triggers,

and functions It also means you need to learn a NET programming language, or at least the

basics of one You should become acclimated to a NET programming language such as C#

or VB.NET to remain effective For example, if you are a DBA trying to debug a performance

problem with a CLR stored procedure, then you need to know the language the stored

procedure is written in to understand the performance problem Features such as

Integra-tion Services and Reporting Services are very much tied to expressions, which are variants

of VB.NET

❑ You need to learn something about XML, including some XPath, and XQuery These features,

introduced in SQL Server 2005, are now getting use in some implementations

❑ Get some practical experience on database mirroring

❑ Of course, you should learn about SSRS, SSIS, and SSAS, even if your shop does not currently

use those features

Beginning with SQL Server 2005 and continuing for SQL Server 2008, these products require a leap

forward in the knowledge a DBA must have to be effective If you want to be a leader, then you must

stay ahead of the game We’ll help you get it done

SQL Ser ver Architecture

In older editions of SQL Server, you had to use many different tools depending on the function you

were trying to perform In SQL Server 2008, the challenge for Microsoft was to avoid increasing the

number of management tools while increasing the features and products that ship with SQL Server

They accomplished this by creating one tool for business-intelligence development (Business IntelligenceDevelopment Studio — BIDS) and another for management of the entire platform, including business

intelligence and the database engine (SQL Server Management Studio) BIDS is based on a lightweight

version of Visual Studio 2008 A new end-user report development tool is also added — Report Designer

SQL Server envelops a large surface now It can act as a reporting tool and store your OLAP cubes

It can also perform your ETL services through SQL Server Integration Services Many people just use

SQL Server for its classic use: to store data SQL Server 2008 can run on Windows XP, 2000, Vista, and

Windows Server 2003 and 2008 Tools such as SharePoint and Office quickly integrate on top of SQL

Server and can provide an easy user interface (UI) for SQL Server data This book covers administration

on each of these tiers

Transaction Log and Database Files

The architecture of database and transaction log files remains unchanged from prior releases The

pur-pose of the transaction log is to ensure that all committed transactions will be persisted in the databaseand can be recovered

The transaction log is a write-ahead log As you make changes to a database in SQL Server, the record is

first written to the transaction log Then, during a checkpoint and at other times, the log data is quicklytransferred to the data file This is why you may see your transaction log grow significantly in the middle

of a long-running transaction even if your recovery model is set to simple (We cover this in much moredetail in Chapter 18.)

Every time SQL Server starts, it performs a recovery process on each database The recovery process

ensures that the data in the database is in a consistent state This means that all committed transactionsare recorded in the data files, and that no uncommitted data is in the data files The recovery process

reads the transaction log, looking for any committed transactions that were never added to the data file

The recovery process adds this data to the data file This is called rolling a transaction forward Recovery

also looks for any uncommitted changes that may have been pre-written to the data files Because the

transaction did not commit, recovery will remove these changes from the data files This is called rolling

a transaction back In SQL Server 2008 Enterprise Edition, this process can be done in parallel across all the

databases on your instance Additionally, a fast recovery feature in Enterprise Edition makes databasesavailable after the roll-forward process is complete

The recovery process also runs at the end of a restore Although there is some confusion and misuse of

terms, even in Microsoft’s Books Online,Restorereplaces a database from backups This only occurs

when you use theRestoreT-SQL command The recovery process runs at the end of the restore and

during startup, to ensure that the database is in a consistent state.

A database may consist of multiple filegroups Each filegroup may contain one or more physical data

files Filegroups are used to ease administrative tasks for a collection of files Data files are divided into

8KB data pages You can specify how full each data page should be with the fill factor option of the

create/alter indexT-SQL command (We go much more into this in Chapter 14.) In SQL Server 2008,

you have the capability to bring your database partially online if a single file is corrupt In this instance,

the DBA can bring the remaining files online for reading and writing, and the user receives an error if he

or she tries to access the other parts of the database that are offline (You’ll learn much more about this in

Chapter 18.)

Historically, the largest row you could write has been 8060 bytes There are two exceptions to this limit:

text,ntext,image,varchar(max),varbinary(max), andnvarchar(max)columns may each be up to

2 gigabytes large, and are managed separately Beginning with SQL 2005, the 8KB limit applies only to

those columns of fixed length The sum of fixed-length columns, and pointers for other column types,

must still be less than 8060 bytes per row However, each variable-length column may be up to 8KB in

size, so the row size can be larger than 8KB in total If your actual row size exceeds 8060 bytes, you may

experience some performance degradation, as the logical row must now be split across multiple physical

8060-byte rows

SQL Native Client

The SQL Native Client is a data-access method that ships with SQL Server 2008 and is used by both

OLE DB and ODBC for accessing SQL Server The SQL Native Client simplifies access to SQL Server by

combining the OLE DB and ODBC libraries into a single access method The access type exposes some of

the new features in SQL Server:

❑ Database mirroring

❑ Multiple Active Recordsets (MARS)

❑ Snapshot isolation

❑ Query notification

❑ XML data type support

❑ User-defined data types (UDTs)

❑ Encryption

❑ Performing asynchronous operations

❑ Using large value types

❑ Performing bulk copy operations

❑ Table-value parameters

❑ Large CLR user-defined types

❑ Password expiration

In some of these features, you can use the feature in other data layers such as Microsoft Data Access

Components (MDAC), but it will take more work MDAC still exists, and you can use it if you don’t need

some of the new functionality of SQL Server 2005\2008 If you are developing a COM-based

applica-tion, you should use SQL Native Client; and if you are developing a managed code application like in

C#, you should consider using the NET Framework Data Provider for SQL Server, which is very robust

and includes the SQL Server 2005\2008 features as well