A SQL Server columnstore index is a column-based non-clustered index used to increase query performance for workloads that involve large amounts of data, like data warehouse fact tables. Learn more.
Read More
SQL Server indexes can be classified in several ways depending on the way they store data, their internal structure, their purpose, and the way they are defined. Learn more.
Read More
Bitmap indexes in Oracle are most helpful in a data warehouse environment because they are generally great (fast) when you are only selecting data. Learn more.
Read More
The bitmap join index in Oracle is a lot like building a single index across two tables. You must build a primary key or unique constraint on one of the tables. Learn more.
Read More
This article exanmies three excellent uses for bitmap join indexes in Oracle: on columns other than the join; on multiple columns; and on multiple tables.
Read More
Function-based indexes in Oracle allow you to create an index based on a function or expression. Learn how this can impact performance.
Read More
While Oracle’s cost-based optimizer generally suppresses poor indexes, problems can still develop when a bad index is used at the same time as a good index. Learn why.
Read More
Choosing to use an index in Oracle depends on how the data and indexes are architected, how the data is distributed within the blocks, and how it is accessed.
Read More
Partitioned indexes in Oracle have the same advantages as partitioned tables: Improved performance. Learn more.
Read More
In Oracle 11g, rebuilding indexes online is much faster, and now is also faster than a DROP and CREATE index. Learn more.
Read More
A partitioned index in Oracle 11g is an index broken into multiple pieces, adding many possibilities to improve performance and increase maintainability.
Read More
Using the Oracle hash index for an exact match in a WHERE clause enables Oracle to access the data by performing one hash function and one I/O instead of multiple I/Os.
Read More