Forum Discussion
Single Index vs. Secondary Column Index | Index strategy over 5000 items
I have many lists that are migrating breaking the magic 5000 items list view threshold. Fun stuff.
- I am unable to add indexes to the lists as it says the item limit is to high. Feels like a catch-22 issue. Is there a way to create them via another method aside from the UI?
- The limit is 20 indexes. I understand that the best indexes to create are the ones that you will use for views. However, does creating to many indexes impact performance?
- I don't understand the concept behind using a single column vs. using a secondary column. What is the best practice around this? When/why would use the secondary column.
Thanks!
eZe
Edit for clairty, I am utilizing O365.
My client had turned up their threshold limit on 2010 to 500,000. Hence the issue.
How about the answer to just this one as it applies to any version of SharePoint:
I don't understand the concept behind using a single column vs. using a secondary column. What is the best practice around this? When/why would use the secondary column.
4 Replies
I exported my AWA like a good SP user...and now I'm left with a list with >50,000. I can't index it (because it's >5,000) and I can't view it. The best I can do is query it from Excel. What am I supposed to do?
- My two cents here:
1. Assuming you are talking about SPO, the only alternative I can think to create such indexes is buy using CSOM but you will probably have the same problems.
2. Indexes are good for views, but can penalize the performance when doing CRUD operations
3. You have to view this such as creating indexes in SQL Tables- As far as I know indexes are the key component for dealing with large lists. Folders are obviously another one. But I didn't get into SPO to use folders (in general) https://support.office.com/en-us/article/Manage-large-lists-and-libraries-in-SharePoint-B8588DAE-9387-48C2-9248-C24122F07C59
I, like everyone in SharePoint land, greatly dislike the fact that a list/library can hold million of items but seems to get "stuck" at 5000.
I am using the indexes as my first step in the guidance for large lists. I am I wrong on that?
Do you have other suggestions for handling large lists?
Is the CRUD issue something you actively architect against? Do you suggest using folders as the only way to utilize a list/library with more than 5000 items? Or do simply not allow for over 5000 items?
