By this stage, you should be familiar with the basics of SQL Server indexes. We've discussed what an Index actually is, as well as some of the most common types you're likely to encounter. Now that we've seen some simple examples of how Indexes can be useful, we're going to delve deeper into nonclustered indexes, as we'll see how they can improve the performance of more complex queries.
2022-11-16 (first published: 2014-11-26)
37,955 reads
Indexes are the database objects that enable SQL Server to satisfy each data access request from a client application with the minimum amount of effort, resulting in the maximum performance of individual requests while also reducing the impact of one request upon another. Prerequisites: Familiarity with the following relational database concepts: Table, row, primary key, foreign key
2019-03-29 (first published: 2011-02-17)
67,269 reads
Now that we've seen the basics of indexing, and taken a deeper dive into Nonclustered Indexes, this Level will focus on searching the table, which will, in turn, will lead us to a discussion of clustered indexes.
2019-03-29 (first published: 2011-06-22)
30,196 reads
Internal and external fragmentation – Causes, cures, and when not to care
2019-03-29 (first published: 2012-02-01)
23,119 reads
Included columns enable nonclustered indexes to become covering indexes for a variety of queries, improving the performance of those queries and with the only overhead being an increase the size of an index.
2019-03-29 (first published: 2011-07-13)
20,003 reads
We've now seen how indexed and non-indexed tables perform in queries, and established "logical reads" as the metric for query performance. Now it is time to explain why logical reads are an excellent metric and also explain what is actually being read.
2019-03-29 (first published: 2019-01-16)
19,205 reads
B: 
C: 