Tips for using indexes in SQL Server 2017 (Part 2) If you create a composite (multi-column) index, try to order the columns in the key so that the WHERE clauses of the frequently used queries match the column(s) that are leftmost in the index. The order of the columns in a composite (multi-column) index is very important. The index will...
Tag: DBCC INDEXDEFRAG
Tips for using query hints in SQL Server 2017
Tips for using query hints in SQL Server 2017 You can use the KEEP PLAN query hint if you want to reduce the estimated recompile threshold for a query. For example, using this hint reduces the number of recompiles when multiple table updates occur. This example shows how you can use the KEEP PLAN hint: SELECT * FROM authors OPTION...
Tips for using indexes in SQL Server 2016 (Part 2)
Tips for using indexes in SQL Server 2016 (Part 2) Drop indexes that are not used. Because each index take up disk space and slow down the adding, deleting, and updating of rows, you should drop indexes that are not used. You can use Database Engine Tuning Advisor to identify indexes that are not used in your queries. Keep your...
Tips for using indexes in SQL Server 2014 (Part 2)
Tips for using indexes in SQL Server 2014 (Part 2) Create a clustered index for each table. If you create a table without clustered index, the data rows will not be stored in any particular order. This structure is called a heap. Every time data is inserted into this table, the row will be added to the end of the...
Tips for using indexes in SQL Server 2014 (Part 2)
Tips for using indexes in SQL Server 2014 (Part 2) Create a clustered index for each table. If you create a table without clustered index, the data rows will not be stored in any particular order. This structure is called a heap. Every time data is inserted into this table, the row will be added to the end of the […]
Tips for using indexes in SQL Server 2014 (Part 1)
Tips for using indexes in SQL Server 2014 (Part 1) Keep your indexes as narrow as possible. Because each index takes disk space try to minimize the index key’s size to avoid using superfluous disk space. This reduces the number of reads required to read the index and boost overall index performance. Use the WAIT_AT_LOW_PRIORITY option with ALTER INDEX statement....