oracle - When may it make sense to not have an index on a table and why? -


for oracle , being relative application tuning, when may make sense not have index on table , why?

there cost associated having index:

  • it takes disk space
  • it slows down updates (index needs updated well)
  • it makes query planning more complex (slightly slower, more importantly increased potential bad decisions)

these costs supposed offset benefit of more efficient query processing (faster, fewer i/o).

if index not used enough justify cost, having index negative.


Comments

Popular posts from this blog

java - nested exception is org.hibernate.exception.SQLGrammarException: could not extract ResultSet Hibernate+SpringMVC -

sql - Postgresql tables exists, but getting "relation does not exist" when querying -

asp.net mvc - breakpoint on javascript in CSHTML? -