Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft SQL Server 2012 Performance Tuning Cookbook

You're reading from   Microsoft SQL Server 2012 Performance Tuning Cookbook With this book you'll learn all you need to know about performance monitoring, tuning, and management for SQL Server 2012. Includes a host of recipes and screenshots to help you say goodbye to slow running applications.

Arrow left icon
Product type Paperback
Published in Jul 2012
Publisher Packt
ISBN-13 9781849685740
Length 478 pages
Edition 1st Edition
Languages
Concepts
Arrow right icon
Toc

Table of Contents (28) Chapters Close

Microsoft SQL Server 2012 Performance Tuning Cookbook
Credits
About the Authors
Acknowledgement
Acknowledgement
About the Reviewers
www.PacktPub.com
1. Preface
1. Mastering SQL Trace Using Profiler FREE CHAPTER 2. Tuning with Database Engine Tuning Advisor 3. System Statistical Functions, Stored Procedures, and the DBCC SQLPERF Command 4. Resource Monitor and Performance Monitor 5. Monitoring with Execution Plans 6. Tuning with Execution Plans 7. Dynamic Management Views and Dynamic Management Functions 8. SQL Server Cache and Stored Procedure Recompilations 9. Implementing Indexes 10. Maintaining Indexes 11. Points to Consider While Writing Queries 12. Statistics in SQL Server 13. Table and Index Partitioning 14. Implementing Physical Database Structure 15. Advanced Query Tuning Hints and Plan Guides 16. Dealing with Locking, Blocking, and Deadlocking 17. Configuring SQL Server for Optimization 18. Policy-based Management 19. Resource Management with Resource Governor Index

Partitioning a table with RANGE LEFT


Let's suppose that you are required to design a database and there is one particular table that is expected to contain millions of rows. To improve the performance, you decide to partition this particular table based on ID column (identity column) in such a way that each partition contains a certain number of rows, rather than having all the millions of rows in one single table. Initially, you decide to start with four partitions, so that they contain rows as follows:

  • Partition 1: Rows with ID values greater than or equal to 0

  • Partition 2: Rows with ID values from 1 to 1,000,000

  • Partition 3: Rows with ID values from 1,000,001 to 2,000,000

  • Partition 4: Rows with ID values from 2,000,001 to 3,000,000

However, in our case, partition 1 is never going to contain any rows, because the value in the ID column will start from 1, increasing by 1, and partition 1 will always remain empty; it is still a good idea to have this partition range for scalability and the future...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image