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 REORGANIZE index


If the fragmentation level is less than 30 percent, one must use REORGANIZE on the index, instead of REBUILD. The REORGANIZE index doesn't produce locks on data pages or tables, leaving the object available for users to use, and takes less server resources and CPU utilization, as compared with REBUILD index.

In short, REORGANIZE is the process of cleaning up current B-Tree (especially leaf level of index), organizing data pages, and defragmenting it. Unlike REBUILD, REORGANIZE won't add any new pages; if this is needed, it just cleans up current pages and defragments them.

Getting ready

To decide whether to use a REORGANIZE index or not, have a look at the fragmentation level of the index first; if it is more than 10 percent and less than 30 percent, you require reorganization of your index. If it is less than 10 percent, you don't need to maintain that index.

How to do it...

Like rebuilding an index, there are several ways to reorganize...