Blog post: 8 minute read
Date last verified: August 2017
[Update November 2017] Microsoft announced Predictive Indexing which will change the way large lists and libraries handle throttling. Column indexes will be added automatically behind-the-scenes as you need them based on views you’ve created, columns you’re filtering on, etc. The net effect of this is the limit has been increased from 5000 up to 20000 (if they are added prior to reaching this limit)! You will see the benefits of this if you are viewing a list/library in the modern experience. Below is the excerpt from Ignite:
Does the remainder of this blog post still apply if the limit in your environment is now 20000? Yes, albeit the risk has been greatly reduced by about 15000 items! You still need to be aware of the limit, plan your lists/libraries accordingly and know if your users will be in the Classic or Modern view while viewing it. I recommend you still add column indexes manually ahead of time if you know you will be filtering a list/library by that column in case you exceed 20000 items and the auto-index hasn’t happened. Once you’re over that limit, you will no longer be able to add a column index.
Note: this blog post is referring to the end-user experience. The 5000 limit still applies for REST calls. Please refer to a great post by Marc Anderson where he goes into more detail – Predictive Indexing comes to Office 365 Lists and Libraries.
I know what you’re thinking… hasn’t this topic been covered enough already Joanne? Please hear me out…I’ve been around the SharePoint space long enough to have read at least 30-40 different blog posts talking about why the list view threshold limit exists in the first place, correct ways to provision libraries so you don’t run into it and how you can set yourself up for success if you exceed it. Heck, I’ve even written one of them! 😉
Here is the official link from Microsoft on managing them (Manage large lists and libraries in SharePoint) and an important excerpt from it explaining where the number 5000 comes from:
To minimize database contention SQL Server, the back-end database for SharePoint, often uses row-level locking as a strategy to ensure accurate updates without adversely impacting other users who are accessing other rows. However, if a read or write database operation, such as a query, causes more than 5,000 rows to be locked at once, then it’s more efficient for SQL Server to temporarily lock the entire table until the database operation is completed.NOTE: The actual number is not always 5,000, and can vary depending on your site, the amount of activity in the database, and your site’s configuration.
When the whole table is locked, it prevents other users from accessing the table. If this happens too often, then users will experience a degradation of system performance. Therefore, thresholds and limits are essential to help minimize the impact of resource-intensive database operations and balance the needs of all users.
I understand the technical reason behind the threshold limit but I still wasn’t satisfied with how well I understood the end-user experience. I suspect there are others out there who, like me, weren’t exactly sure what an end-user would see once the threshold limit was exceeded. Yes, I knew it would throw an error but I wanted to test out Microsoft’s recommendations in the link above to see if I could get around the limit if I designed a library using them. I not only wanted to document my observations but since my Office 365 tenants seem to be straddling both classic and modern worlds right now, I also wanted to capture some Modern library screenshots and document what the differences, if any, were between it and a Classic one.
Why this and why now?
I’m working with a team on a large migration effort to migrate shared network drive content into SharePoint Online. We decided not to take the “lift and shift” approach (right decision by the way), but to take this golden opportunity to clean-up what was there and look at ways to introduce some Information Architecture prior to migrating it into SharePoint.
Like most organizations, even after an aggressive clean-up there’s going to be some BIG network drive folders to migrate and like it or not, no matter how much we are trying not to, some of them are going to end up in the same document library. Due to this, our team really needs to understand the list view threshold, how we can mitigate the risk of running into it and what we will see if/when we hit that wall.
To that end, this past week I set out to test the List View threshold – I wanted to see it in action myself. No matter how many other blog posts I’ve read on this subject, none of them demonstrated to me clear enough what the end-user experience would be like. Some of the questions I had:
- If you put a column index on something you’re filtering or grouping on, can you go over the 5000 limit? Some blog posts make it sound like it would, but I needed to see it with my own 2 eyes.
- On indexed columns, will column header filters work as expected once you exceed 5000 items?
- I’ve seen many blog posts refer to the ‘All Documents’ view and how you should be careful leaving this as the default view for a big library. If it’s only displaying items in batches (the default), why does that matter? Is this still a problem?
- What benefit do folders provide in the context of the threshold limit? (Note: I’m not factoring in other reasons you would use folders like security)
This test is in a SharePoint Online environment which means, unlike an on-premises environment:
- I have no option to increase the threshold
- I cannot execute a view with increased limits as an administrator
Disclaimer: this post is based on my observations during a non-scientific test on a large SharePoint Online library. If your experiences have been different than what I observed, please let me know. There are many variables to take into account and I want to ensure I’ve documented the correct findings.
Following are the steps I did for this test and the results I observed.
Set-up prior to migration
- I created one document library called Big Library with 4 root folders in it called East, West, North, and South.
- I created 2 choice columns on the library, both required:
- Vendor Rating
- I created 2 separate column indexes for the above choice columns. (Everything I’ve read indicates you need to do this BEFORE reaching the threshold. This makes sense since the creation of the index can itself exceed the threshold if you wait to do it AFTER the item count has exceeded 5000)
- I left the “All Documents” view with the default settings which is to display within folders in batches of 30.
- I created 2 Grouped by views. One to group by Region; the other to group by Vendor Rating. I changed both of these views to display “without folders in all folders” since this is typically how I see many Grouped by views being configured in real-world scenarios in libraries with folders. I left the default setting to display in batches of 30:
- Using Sharegate (shameless plug for a great migration product by the way), I migrated 4996 items into the folder called East. We’ll call this the ‘migration folder’ from this point forward in the post. Why 4996 items? The threshold will start to kick in after 5000 items. Since you also have to include folders in the item count, migrating in 4996 items would put the total item count for the library at exactly 5000 items.
- During the migration, I updated the metadata values as follows:
- Region was set to East for all 4996 items (column default value)
- Vendor Rating was set randomly across all 4996 items:
- Bronze: 2149
- Silver: 523
- Gold: 2324
- As expected, I now see the familiar warning in library settings:
The following section describes what I observed while using the Modern library experience…
Post Migration – 5000 items
I navigated into the migration folder with the default All Documents view. I immediately noticed it did not adhere to the batch limit specified on the view. It returned far more than 30 items and in fact I scrolled down and gave up before I actually hit the bottom. It did display the first couple of screens of results fairly fast. The further I went down the list, the slower it got.
I switched to the Grouped by Region view and, as expected, it rendered successfully:
I switched to the Grouped by Rating view and, as expected, it also rendered successfully:
Both of the above grouped by views rendered very fast.
Post Migration – 5001 items
I uploaded one additional document into the migration folder.
- Total item count in library: 5001 items
- Total item count in migration folder: 4997 items
I navigated into the migration folder and the All Documents view continued to behave as it was before, not recognizing the batch limit of 30 items.
I navigated to the Group by Region and the Grouped by Rating views. As expected, they both threw the ‘List View Exception’ error since the library is now over 5000 items and the view is displaying all items without folders in all folders:
I went back to the root of the document library and selected the same 2 Grouped by views. I was extremely surprised to see that both of the views displayed without issue when I was at the library root (not in a folder), but at this level they showed an “approximation” of the group count:
Before adding more items, I changed both Grouped by views to display “inside folders” instead of the current setting of “without folders”. Once I did this, the views returned to rendering successfully when I navigate inside a folder (I am still under 5000 in the migration folder). This is what I see for both views when in the Migration folder:
I switched back to the All Documents view to test out the column heading dynamic filter options available on the view. The Filter by options to filter on specific Vendor Rating values worked extremely well and was lightning fast. The Group by Vendor Rating option did not produce the results I was expecting:
It showed the Bronze vendor rating correctly, but nothing for the silver and gold. (Albeit this may be a current limitation of the Modern view):
I then used the metadata filters available to me on the modern library’s filter pane. To open up the filter pane, click the filter icon on the top right-hand side of the library. This worked extremely well and was fast in all tests I did. I would highly recommend teaching end-users how to use these filters in large libraries.
Post Migration – 5005 items
I uploaded an additional 4 documents into the migration folder so I was now exceeding the 5000 item count within the folder.
- Total item count for library: 5005
- Total item count in migration folder: 5001
The All Documents view in the folder continues to behave as before. It did not adhere to the 30 item limit but it did not fail and returned the first few screens of results to me very fast.
Within the migration folder, the Grouped by views continue to render successfully and give the exact count of each grouped by column. This surprised me!!! Isn’t there supposed to be a threshold at 5000? Yes, but I created an indexed column on the column being grouped by so (I assume) this is allowing me to get around this threshold limit. I tested this out further by uploading an additional 8 documents (the folder now has 5009 items) and the view continued to render successfully.
My thoughts immediately went to this excerpt from Microsoft I quoted above: The actual number is not always 5,000, and can vary depending on your site, the amount of activity in the database, and your site’s configuration.
Could this be what’s happening? Perhaps I’m able to render the view exceeding 5000 right now, but if the site/database became busier perhaps it wouldn’t work anymore. This alone leads me to believe that it is best to stay under that magical 5000 number if at all possible.
[Update] I’ve since uploaded another 1500 documents into this folder for a total of 6500 items within one folder. The views continue to render successfully as I’ve described them above.
What does this look like in Classic view?
My next question is if this behaved or looked any different in the same library set to the Classic view. I will run thru the same test when the threshold limit is exceeded in Classic mode.
The All Documents view adheres to the 30 item limit consistently.
Did the Grouped by views work? It depends.
If you are within a folder and there are over 5000 items and the Grouped by view is specified as ‘Show all items without folders in all folders’, it will render successfully but it will give you a throttled result (newest) with this message on top of the view:
If you change any Grouped by views to ‘show all items inside folders in all folders’, you will see this threshold error when you navigate into a folder with >5000 items:
The Classic and Modern experiences are very different from each other in this test – the Modern view experience is a definite improvement for the end-user in my opinion.
Returning to my initial questions:
Question 1: If you put a column index on something you’re filtering on or grouping on, can you go over the 5000 limit?
Answer: Short answer, yes. The column index will help you if you are using metadata filtering on your document results. Also, although it appears not to help with Grouped by views in classic view (the view renders, but is throttled), it does help when in a modern view if the view is set to “view all items inside folders in all folders”.
Question 2: On indexed columns, will column header filters work as expected once you exceed 5000 items?
Answer: Yes. Not only did the column header filters work as expected, but the metadata filters in the filter pane worked as well. Both techniques filtered results very fast.
Question 3: I’ve seen many blog posts refer to the ‘All Documents’ view requesting it not be the default view if it is in a big library. If it’s only displaying items in batches (the default), why does that matter? Is this still a problem?
Answer: Although the All Documents view continued to render for me once the library reached 5000, the more I scrolled down the list the slower it got. In the modern view it did not adhere to the display batch limit. Options for configuring the All Documents view:
- remove it as the default view
- limit the # of items to display at 5000
- favor the use of metadata filters to filter your data
- replace it with a filtered view if you can to reduce the # of items being returned
Question 4: What benefit do folders actually provide in the context of the threshold limit? (I’m not factoring in other reasons for folders like security)
Answer: Microsoft recommends using folders to keep you under the 5000 limit to help ensure good performance. A light-weight use of folders in addition to metadata is a great compromise to organize content at a high level if you are in a large library. Thru my testing, it appears if I use folders and Grouped by views in a Modern library, I should ensure the view setting are set to “view all items inside folders in all folders” and then the result counts appear to be correct. In fact, in the Modern view, I was able to upload > 5000 items within one folder and still group by a column in that folder with all items being accounted for. Would I recommend pushing this limit and storing more than 5000? No, I still would not!
Another reason for using folders is for setting default column values based on the folder name. The values can then be used for metadata filtering.
My 8 takeaways…
- Design document libraries to stay under 5000 if possible so you don’t get into this hot mess in the first place. 😉 (I have previously blogged about options for designing libraries – Multiple Libraries, Folders or Metadata?)
- Even though my testing proved you can in fact exceed 5000 items in a view if using indexed columns, I still wouldn’t recommend exceeding it. Err on the side of caution when dealing with performance.
- In a large library, favor using search and metadata filtering rather than relying on Grouped by views for end-users. In large libraries, Grouped by views aren’t an effective way to find documents anyway.
- If you are using a combination of folders and metadata, ensure any Grouped by views are set to ‘view all items inside folders in all folders’ if in a Modern library. If you are still in a classic library, you can set the Grouped by views to ‘view all items outside folders in all folders’ to show the newest (throttled) results.
- Set up column indexes ahead of time. Use these columns for filtering your list and, if required, Grouped by views.
- Limit the # of items in all views to 5000. This is good insurance in case you go over 5000 items.
- An item is an item is an item. The item count includes folders. (You can’t have more than 5000 folders at the same level of a library or else it will ALSO exceed the threshold limit. I have never seen this personally, but I know others who have, particularly in automated solutions)
- The behavior when the list view threshold is exceeded appears to be different depending on if you are viewing a classic or modern library. (I prefer the modern view experience simply because the results don’t appear to be throttled). It is also my assumption the modern view experience will only improve over time for end-users.
Thanks for reading and good luck with those migrations!
Hello, excellent work here! Thank you very much!
Do you know any workaround to a doc library that passed the treshold without any index column before passing this 5000 itens limit?
No easy workaround. You’ll have to get the number of items under 5000 before adding an index. Do you have a migration tool to assist like Sharegate? You could move some items out to get it under 5000, create the index and then move them back. Just a thought.
Thanks for the article Joanne. I too have scoured many articles on the web to explicitly understand the list/library item threshold limit. You are correct, the best method is to run an experiment (like you did) and see the ramifications directly (as I’ve done myself). Your article provides such good details that I added it to my Pocket account for offline reference.
Excellent work – thank you for this! It has helped me to understand an otherwise tricky concept.
Does this threshold apply individually to each Sahre Point Team Site? or are we talking about Share Point as a whole?
The list view threshold limit applies to each list on a site. Every list in your tenant must comply with this threshold. In an on-premises environment, you have control over what the limit is at a web app level (configured thru the Resource throttling menu option in Central Admin) however you should be cautious when increasing it due to performance degradation.
Joanne, sorry to use an old thread but I think that my question fits here.
We have document libraries with a lot more than 5000 items in SharePoint Online and they work fine. However, I found out late last week that, if we add a column in a large list, there is no way to delete it.
It is so easy, in a modern library, to add field in the list that a user did it by mistake in a 65000+ documents lib. Now, I am stuck with that field.
Ever been in that situation? I logged a call at Microsoft to see if they can help.
Hi Benoit… I’ve never been in this situation. Microsoft support sounds like the best route.
I have a form in which user submits a request with info and documents. My DL has reached 5000 limit. Will there be any issue in saving the data in DL when user submits a new request from now on??
It’s not a problem to store more than 5000 items, in fact a library can have up to 30 million items. Anytime you’re querying the library (programmatically, thru the UI on a view) and you want to return >5000 items, you may run into a problem in certain situations.
Hi Joanne, One of my clients hit the limits with libraries with over 100,000 documents. Libraries with about 25.000 documents worked fine. Do you know if the 20,000 you mentioned in your post has been increased in recent months?
Further to my earlier comment making changes through the modern UI (e..g column formatting works even for large libraries) through the Library settings this fails.
Thanks for your post. Like yourself, I have read countless blogs on this topic and yet, I still don’t understand this confidently.
I understand that a list view can only display 5000 results at one time. But what I can’t understand is whether there is any issue with using the ‘All Documents’ default view, and using sub folders to ensure there is no single directory which has > 5000 items. So for example:
Root folder of the document library has 3 sub folders named ‘folder 2A’, ‘folder 2B’ and ‘folder 2C’.
‘folder 2A’ has 4000 files and a folder named ‘folder 3A’. ‘folder 3A has 4000 items’ and a folder named ‘folder 4A’. ‘folder 4A’ has 3000 files.
‘folder 2B’ and ‘folder 2C’ both have 3000 files.
In this above example, using the default ‘All Documents’ view, which has ‘Show items inside folders’ selected – and also using the modern experience, should this cause any issues? We typically don’t use any custom views and don’t need to filter documents, we just use it as a regular file share as if you were browsing a network share with typical sub folder structure.
Hi Matthew, I don’t think you’ll run into issues. Remember it’s a list VIEW threshold which means as long as the view isn’t trying to display more than 5000 items it should be ok. Sounds like you’re under that as long as you’re viewing the library using the folder structure. Do let me know in this thread if you experience something different.
Thank you for replying. This is as I suspected, I just couldn’t find confirmation of this anywhere. I find it disconcerting that when going to ‘site contents’ > then clicking ‘settings’ on a document library with > 5000 items, you get this list view threshold warning message. If the default ‘All Documents’ view is set to ‘Show items inside folders’ and there are no folders which have > 5000 items to display, it would be useful if it recognised this.
Kinda makes sense they put the warning there imo. You could create a custom view or modify the All Documents view and then you could easily bump into the threshold limit. The warning may help some end users know they have to manage the large library a bit differently now so probably worth having it there.
And they may not want to take the performance hit to pre-check all of the current view settings to determine if they should/shouldn’t display that warning. But who knows…