Remove the list view threshold (5000 by default)
This limit has always been a bit laughable, and is even more so as we develop more client side applications. In SharePoint 2007 we didn't have this limit and were allowed to make our own mistakes. Now that hardware is so much more powerful, we need this limit removed so that we can build enterprise-class applications.
We are continuing to make our large list experiences better, please keep the feedback coming.
Spring 2018 update:
- We now support being able to manually add indexes to lists of any size (increased from lists up to 20,000 items previously).
- Starting with the February release of the Office 365 Excel client, you will be able to export your full list instead of getting cut off part of the way through.
What we are working on now:
- Predictive indexing will start to work for lists larger than 20,000 items so your views will automatically cause the right indexes to be added to your lists.
In our backlog:
- Being able to index/sort/filter by lookup column types (like person, lookup or managed metadata columns) without being throttled.
- Making sure that our REST APIs support querying in ways that will guarantee that the call will not be throttled.
For a general update on large list capabiltiies, the video on myignite.microsoft.com/videos/53861 (focusing on large lists at 42 minutes and 25 seconds) describes some of the changes that we delivered back in the second half of 2017:
- Modern UI now has a lot of support for adding indexes to large lists and libraries on the fly, reducing the number of throttling errors experienced by our users, and some new UI for browsing through items in large lists with our paging model
- SharePoint runs predictive indexing jobs to automatically add indexes as lists get larger based on your view definitions, and updates these indexes when you add/update your views
Looking forward to receiving more of your feedback.
Simple answer is do not use lists and move to a database for all your data requirements. SharePoint lists are nothing short of a joke.
Eric Fultyn commented
List throttling the way it is implemented, while good intentioned, seems to cause more problems for end users AND administrators than it solves. If a list is over the threshold limit, it won't let you do anything without upping the threshold, rendering the list useless. When you up the limit, you defeat the purpose of having that limit in the first place. I don't know if getting rid of a limit is necessarily the answer, but it should behave more like the maximum page amount that one can request at one time, rather than the maximum total items you can have before you are blocked from doing anything. As a farm administrator and a developer, I have seen absolutely no benefit to the current implementation. My vote is to fix it or forget it.
This request was already voiced here: http://sharepoint.uservoice.com/forums/282887-customer-feedback-for-sharepoint-server/suggestions/7077672-increase-remove-throttling
Agree, we had a lot more issue to convience the client when we built Global Record Management system for them, though we used managed metadata and term base navigation to overcome the challenge
Martial Dautremont commented
We need MS to provide a solution to overcome this limitation.
Yes, SP is no DBMS but business cases often deal with more than 5000 results.
Combined with the 8 lookups limit, it is a big burden !!!
Shogo Akimoto commented
Yes, this is the lock escalation limit on the SQL Server. But expect to impliment other ways (like paging) for removing this limit even if it will be performance down.
Trevor Seward commented
This is a SQL Server limitation, where requesting >5000 items introduces a table-level lock, versus a row-level lock for <5000 items.
Kushal Arora commented
Throttling is a big pain for many customers. If you somehow increase the throttling (no. of items in a list and no. of lookup columns) limit without impacting the performance then it will be beneficial for a larger audience.