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.
Subscribe to:
Post Comments (Atom)
Stop Memorizing SQL Part 3 : A Practical SQL Cheat Sheet for Beginners
A Practical SQL Cheat Sheet for Beginners When learning SQL, students often struggle to remember the correct syntax during exams or practic...
-
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...
-
Move distribution database to another drive: There are scenarios in SQL server Replication that we need to move datafiles and logfiles of di...
-
* Stored procedures generally result in improved performance because the database can optimize the data access plan used by the procedure an...
No comments:
Post a Comment