<div>
When you have a slow performing query that uses a single field in the where clause then it is a good field on which to create the index in some cases...<br />
<br />
No need to be unique as the data are not unique obviously. <br />
Index does not help when the WHERE condition does not reduce the number of retrieved records, e.g.<br />
<br />
WHERE SomeIntegerColumn &gt;&nbsp;-2147483648 &nbsp;-- all integers fulfill this condition <br />
<br />
The best index performance is achieved when you retrieve just a few rows out of many rows in the entire table, e.g.<br />
<br />
You may read more e.g. here: <a href="http://sqlmag.com/database-performance-tuning/indexing-dos-and-don-ts" rel="ugc">http://sqlmag.com/database-performance-tuning/indexing-dos-and-don-ts</a><br />
<br />
Clustered indexes are about the physical records order. They are slowing down the table creation (new records insertion) but the positive effect is they keep related records together and reduce the number of physical reads if your queries are retrieving all these related records at once. Example is e.g. Order lines having the clustered index on Order ID (+ Order Line ID to have it unique as this is better than the non-unique clustered index).
</div>


<div>
<div class="content wysiwyg-content">
When I have a slow performing query that uses a single field in the where clause, is that a good field on which to create a Unique Index?<br />
<br />
Otherwise, what are a few rules of thumb when deciding which field could boost performance by having a Unique Index?<br />
<br />
Now, please explain how a Clustered Index fits in? What big problems do they solve?<br />
<br />
Thanks.
</div>
</div>


When I have a slow performing query that uses a single field in the where clause, is that a good field on which to create a Unique Index?

Otherwise, what are a few rules of thumb when deciding which field could boost performance by having a Unique Index?

Now, please explain how a Clustered Index fits in? What big problems do they solve?

Thanks.

When to use a Unique Index? A Clustered Index?

Databases are organized collections of data, most commonly accessed through management systems including schemas, tables, queries and processes that allow users to enter and manipulate the information or utilize it in other fashions, such as with web applications or for reporting purposes.

Databases

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.

Microsoft SQL Server

Microsoft SQL Server 2008 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. Major improvements include the  Always On technologies and support for unstructured data types.

Microsoft SQL Server 2008

T-SQL

SQL (Structured Query Language) is designed to be used in conjunction with relational database products as of a means of working with sets of data. SQL consists of data definition, data manipulation, and procedural elements. Its scope includes data insert, query, update and delete, schema creation and modification, and data access control.