Book Image

Microsoft SQL Server 2012 Performance Tuning Cookbook

Book Image

Microsoft SQL Server 2012 Performance Tuning Cookbook

Overview of this book

As a DBA you must have encountered a slow running application on SQL Server, but there are various factors that could be affecting the performance. If you find yourself in this situation, don't wait, pick up this book and start working towards improving performance of your SQL Server 2012. SQL Server 2012 Performance Tuning Cookbook is divided into three major parts -- Performance Monitoring, Performance Tuning, and Performance Management--that are mandatory to deal with performance in any capacity. SQL Server 2012 Performance Tuning Cookbook offers a great way to manage performance with effective, concise, and practical recipes. You will learn how to diagnose performance issues, fix them, and take precaution to avoid common mistakes. Each recipe given in this book is an individual task that will address different performance aspects to take your SQL Server's Performance to a higher level.The first part of this book covers Monitoring with SQL Server Profiler, DTA, System statistical function, SPs with DBCC commands, Resource Monitor & Reliability, and Performance Monitor and Execution Plan. The second part of the book offers Execution Plan, Dynamic Management Views, and Dynamic Management Functions, SQL Server Cache and Stored Procedure Recompilations, Indexes, Important ways to write effective TSQL, Statistics, Table and Index Partitioning, Advanced Query tuning with Query Hints and Plan Guide, Dealing with Locking, Blocking and Deadlocking and Configuring SQL Server for optimization to boost performance.The third and final part gives you knowledge of performance management with help of Policy Based Management and Management with Resource Governor.
Table of Contents (28 chapters)
Microsoft SQL Server 2012 Performance Tuning Cookbook
Credits
About the Authors
Acknowledgement
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Index

Enhance index efficiency by using the REBUILD index


Rebuilding an index will do nothing, but just drop the current index and recreate it internally, so that all fragmentations go away, statistics are updated, and physical sorting order in data pages are in co-ordination with each other. It compacts data pages, fills them up with a proper Fill Factor, and adds new data pages if needed. All these things will help in faster data retrieval, but at the same time this is a really very resource-centric job and takes a very long time to finish on large tables with millions of rows.

Getting ready

Decide first whether it is really necessary to rebuild an Index. If it is worth rebuilding an index, only then should one go for this option. Otherwise, use the REORGANIZE index, because the REBUILD index can use lots of server resources. If fragmentation is greater than 30 percent, it is good to use the REBUILD index.

Rebuilding an index can be done in two different modes and it is better to decide what mode...