Torsten Strauss

ABOUT ME

Microsoft SQL Server Expert

My name is Torsten Strauß, a Microsoft Most Valuable Professional for Data Platform from Germany. At the turn of the millennium, I discovered my passion for the Microsoft SQL Server product suite. I am specialized in Microsoft SQL Server performance tuning, troubleshooting and T-SQL programming. For the past decade I have also worked with Microsoft Integration Services and Reporting Services and I have collaborated with Sarpedon Quality Lab®, a company endorsed as the only Microsoft Certified Solutions Master for the Microsoft Data Platform in Germany. You can meet me at international and national user groups and conferences where I share my knowledge and experience with the Data Platform community.

TRAINING

Individual Training For Individual People

With Microsoft SQL Server products, you can do amazing things – sometimes it only needs a little support. As a Microsoft Certified Trainer and Microsoft Certified Solutions Expert, I offer professional training on SQL Server performance optimization, query tuning and data integration with Microsoft Integration Services. To stay up to date with this rapidly changing technology, I regularly attend conferences and training sessions from other experts myself.

BLOG

Learning By Sharing

In my experience, it is best to learn by sharing your knowledge. Feel free to review my blog posts, ask questions, and leave feedback. Just drop me a note if you are interested in a particular topic.

2019-07-07    Microsoft SQL Server    SQL Server Query Tuning, Missing Index Feature

This will be my last blog about the limitations of the missing index feature. This time I will demonstrate that the missing index feature will not suggest filtered indexes. Filtered indexes reduce the index size and thus the storage allocation in the data file is reduced. Rebuilding or reorganizing these indexes also requires fewer resources. So it's worth creating filtered indexes when possible.The following example will prove that the missing index feature will not consider creating filtered indexes.

2019-04-22    Microsoft SQL Server    SQL Server Query Tuning, Missing Index Feature

This will be my penultimate blog about the limitations of the missing index feature and this one will be short.Before we start, let us clarify some terms so you can better understand the table we are going to create.The data types real and float are imprecise data types for use with floating point numeric data. Floating point data is approximate; therefore, not all values in the data type range can be represented exactly.Non deterministic columns are computed columns which may return different results each time they are called.

2019-02-10    Microsoft SQL Server    SQL Server Query Tuning, Missing Index Feature

In the last post you saw that the missing index feature does not consider the order for columns to be used in an index.In this blog I will explain another limitation of the missing index feature - it reports only include columns for some queries.SQL Server supports two kind of row store indexes - the clustered index and then non-clustered index. It is important to understand the difference between these two indexes in order to implement the right index type to improve reading performance.

2018-12-31    Microsoft SQL Server    SQL Server Query Tuning, Missing Index Feature

In the last post you saw that the missing index feature does not consider trivial plans.In this blog I will explain another limitation of the missing index feature - it does not specify an order for columns to be used in an index.SQL Server can only benefit from a row store index if the key columns are in the correct order. The order of the columns of an index determines whether SQL Server chooses an index scan or seek. Scanning an index simply means that the storage engine of SQL Server will read all index pages and filter the desired records afterwards (residual predicate)

2018-10-12    Microsoft SQL Server    SQL Server Query Tuning, Missing Index Feature

In the last post you saw that the missing index feature does not gather statistics for more than 500 missing index groups.This time I am going to reveal another limitation which is not even documented - the missing index feature does not recommend missing indexes for trivial queries.SQL Server has to create an execution plan before executing a query because it has to evaluate the different available physical iterators depending on the cardinality estimation, supportive indexes, available hardware resources and instance settings to find a good enough plan.

2018-10-06    Microsoft SQL Server    SQL Server Query Tuning, Missing Index Feature

Implementing the right indexes will improve the execution time and IO reads for a Select, Update or Delete. Unfortunately sometimes it is not that easy to identify missing indexes without having a deep understanding about Query Execution Plans. That is why SQL Server gives us a hint about missing indexes in an Execution Plan.Sounds beneficial but in this blog post I will proof that it is not always a good idea to rely on these index recommendations.According to Microsoft, there are the several Limitations for Using the Missing Indexes Feature.

previous arrowprevious arrow
next arrownext arrow
Shadow
Slider

MEET ME

Let’s Get To Know Each Other

You can meet me at conferences and user groups where I love to share my experience and knowledge about Microsoft SQL Server. So far, I have spoken at more than 80 conference and user groups and do not intend to change anything in the near future. I look forward to meeting you in person.

Upcoming Events

CONTACT

Let’s Work Together

Big things have small beginnings. Let us find out what we can achieve together.

inside-sqlserver recommends Sentry One to make your SQL Server faster