Member Login
  • Products
    • Qure Suite
    • Qure Analyzer
    • Qure Optimizer
  • Downloads
    • Qure Analyzer (Free)
    • Qure Optimizer (Free Trial)
  • Support
    • Contact Support
    • Frequently Asked Questions
    • Limitations and Known Issues
  • Resources
    • SQL Server Articles
    • Whitepapers
    • Videos and Tutorials
    • Attend an Online Demo
    • inTune eMagazine
    • SQL Server Tuning Blog
  • Learn More
    • About Workload Tuning
    • SQL Server Tuning
    • SQL Server Performance
    • SQL Server Performance Tuning
    • Tips
  • Company
    • About DBSophic
    • Management
    • Partners
    • News
    • Success Stories
    • Customer Testimonials
    • Selected Customers
  • Contact Us
Subscribe to blog

SQL Server Tuning Blog

By SQL Server MVP Ami Levin

Posted by Ami Levin
Ami Levin
My name is Ami Levin, and I've been working with SQL Server for over 15 years. I
User is currently offline
on Thursday, 26 January 2012
in SQL Server Tuning
  • Hits: 243
  • 0 Comments
  • Subscribe to updates
  • Print
  • Bookmark

The Hidden Menace of CREATE INDEX

Tweet

Are you experiencing performance bottlenecks? Is this query taking forever to complete? Most DBAs would start their resolution attempts with one of SQL Server’s most powerful features – Indexes. Indexes are such an effective mean that a small change could mean a world of a difference in performance. Most DBAs are also aware that adding indexes will cause some degradation of data modification operations as more indexes need to be updated to reflect the changes. However, few are aware that sometimes adding indexes can be a double-edged sword, with far reaching implications on performance, and not always for the best… This article will help you understand a hidden danger of adding more indexes, that can result in surprising effects on your workload. It tells a story of a production server that was brought to its knees with the addition of a single, innocent looking index.

0 votes
Tags: Articles
  • About the author
  • Related Posts
Ami Levin
My name is Ami Levin, and I've been working with SQL Server for over 15 years. In 2006 I was awarded the SQL Server MVP award.I am also the CTO (and co-founder) of DBSophic. I hope you will find this blog interesting and useful. Your feedback will be highly appreciated.
  • View author's profile
  • Subscribe to blogger updates
  • SQL Server Logical Reads – What do they really tell us?

    If you’ve ever used SQL Trace, STATISTICS IO or any other SQL Server monitoring, you should know what logical reads mean. Or do you? Logical reads ser...
    By Ami Levin on - Dec 05 in SQL Server Tuning
  • Physical Join Operators in SQL Server

    Writing a query that joins several tables is easy, right? There are just a few major join types and their syntax is pretty straightforward and clear. ...
    By Ami Levin on - Dec 21 in SQL Server Tuning

Comments

Please login first in order for you to submit comments

Biography

Ami Levin
My name is Ami Levin, and I've been working with SQL Server for over 15 years. In 2006 I was awarded the SQL Server MVP award. I am also the CTO (and co-founder) of DBSophic. I hope you will find this blog interesting and useful. Your feedback will be highly appreciated....
View all posts

Latest Posts

  • Qure Analyzer V1.5 Beta Available
    About a year ago, we launched Qure Analyzer V1.0 (previously called Qure Workload Analyzer). Si
    Read More
  • Variable Size Data Types and Memory Grants
    Yesterday, at our 118th Israeli SQL Server User Group Meeting, Adi Cohn delivered a session on commo
    Read More
  • Index rebuilds and statistics updates
    An interesting discussion came up lately on the MVP private forums regarding index rebuilds, recompi
    Read More

Tag Cloud

Articles data types Maintenance Performance SQL Server 2012 Qure Analyzer Publications Statistics TSQL2sDay HA/DR iPad common pitfalls Performance SQL Graphics Statistics Announcements RTM MVP

Blog Calendar

Loading ...
© 2011 DBSophic Ltd. All rights reserved. | Legal