Is adding indexes to a SQL Server ever a bad idea?
Posted
by Aerik
on Stack Overflow
See other posts from Stack Overflow
or by Aerik
Published on 2010-05-21T01:12:42Z
Indexed on
2010/05/21
1:20 UTC
Read the original article
Hit count: 368
We have a mid-size SQL Server based application that has no indexes defined. Not even on the the identity columns. I suggested to our moderately expensive application consultant that perhaps we might get better performance (particularly as our database grows) by creating some indexes on appropriate fields, and he said:
"Indexes will significantly impact other areas of the application and customers should not create them under any circumstances."
Anybody ever heard of anything like this? Are there ever circumstances where one should not create any indexes? I can see nothing special about this app - it's got int identity columns, then lots of string columns, bunch of relational tables but nothing special or weird that I can see.
Thanks!
© Stack Overflow or respective owner