Using LIKE to Suppress an Index in Oracle 11gR2
LIKE, in some cases, uses an index, while in others, it does not. Learn how this can impact Oracle database performance.
Read More
LIKE, in some cases, uses an index, while in others, it does not. Learn how this can impact Oracle database performance.
Read More
When a single index in Oracle has multiple columns that are indexed, it is called a concatenated or composite index; however, you should be careful when selecting the order of the columns in the index.
Read More
Oracle 11gR2 allows you to turn off the index (make it invisible), yet continue to maintain the index (during any DML—INSERT/UPDATE/DELETE) in case you need to turn it back on quickly.
Read More
Too many SQL Server indexes create additional overhead associated with the extra amount of data pages that the Query Optimizer needs to go through.
Read More
The execution plan selected by the Query Optimizer may or may not make efficient use of indexes, or it may not use indexes at all. The following sections describe how execution plans can use indexes.
Read More
Learn how to perform SQL Server Index cleanup tasks on a regular basis to prevent excessive fragmentation.
Read More
Learn how you can monitor SQL Server 2012 index fragmentation through the provided DMVs.
Read More
Learn how to use SQL Server 2012 partitioned tables to spread a single table over multiple partitions.
Read More
Learn about a clever Oracle indexing strategy for queries that involve “IS NULL” criteria.
Read More
Learn how cleaning up unused indexes can impact Oracle performance.
Read More
Learn about how invisible index in Oracle 11g can impact performance.
Read More
Duplicate indexes in SQL Server can create unneeded overhead. Learn how exact duplicate indexes affect performance.
Read More