SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a screen where the user will be querying using all columns in the list. Should i index every column.

What are the rules around this?

Would there be any performance problems?

share|improve this question
up vote 3 down vote accepted

NO, Index the columns that you search and filter on, try and stay at a maximum of 2.

This works exactly like a database, the more indexes the slower updates and additions become.

Columns that you might want to index are:

Any column that appears in JOINS or WHERE statements.

share|improve this answer

As you probably are aware use of Indexing is meant to increase performance, particularly in querying, filtering and sorting in large lists, avoiding database scanning, etc. But also over-doing could fall in other extreme (beyond the actual limit of 20), e.g. remember that each update in the structure would require adding a row in NameValuePair table in Content database, which grows extremely fast. Have a look at this

You should understand the fact the there are Simple or Compound, as a rule: - Create single indexes for a single field to filter e.g. with the CQWP and create compound indexes for queries that are going to filter two columns.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.