Clustered index guidelines:
Good when queries select large number of adjacent rows (range queries)
Create on the frequently used columns (in JOINs and WHERE with “=“,
“<“, “>“, “BETWEEN”)
If number of returned rows is small – non-clustered index may be as
efficient
Preferred on narrow and highly selective columns..
Remember cost of maintenance:
Updates reorganize the table
Performance impact
Causes index fragmentation over time
Non-clustered index guidelines:
Create for frequent search columns
Use on narrow and highly selective columns
Place on foreign key constraints (for join queries)
Check the workload for “covering” queries
Consider adding included columns
The drawback: maintenance cost
Frequent updates will ruin perf where there are too many indexes
Evaluate benefits of [not] indexing small tables
This blog is useful for Database, Business Intelligence, Bigdata and Data Science professionals.
August 28, 2010
Subscribe to:
Posts (Atom)
Image Similarity Search using Vector embeddings and Cosine similarity
Image embeddings capture visual features (shapes, colors, objects, textures) Image embedding models are typically CNN or vision transformer...
-
Database Mirroring and index maintenance in AWS Database Mirroring, the database has to be in the full recovery mode, so all index rebuilds...
-
Move distribution database to another drive: There are scenarios in SQL server Replication that we need to move datafiles and logfiles of di...
-
1. To change the scheduled time of oracle job and force it to run at certain time, use the set_scheduler_attribute procedure.e.g. To start j...