Comments on: Can you really have more than 2000 items per folder in SharePoint now?

By: saif

saif — Wed, 03 Mar 2010 04:54:37 +0000

I appreciate the effort you did in publishing this documentation.very informative post. keep it up!

By: Andreas Grabner

Andreas Grabner — Fri, 23 Jan 2009 13:21:37 +0000

You can checkout my blog series about SharePoint List Performance at http://blog.dynatrace.com/category/net/sharepoint-net
This series looks into the SharePoint Object Model to highlight what is actually going on between the SharePoint Servers and the Content Database
It also discusses the 2000 items “myth”

By: SharePoint 2007 : Pourquoi une limite à 2000 elements ? , Philippe Sentenac [Usual Coder]

Tue, 22 May 2007 09:38:20 +0000

[...] trouverez d’autre infos dans le genre dans le document ci-dessus et dans ce post del.icio.us tags: Technet, SharePoint, Limit Technorati tags: Technet, [...]

By: Keith Richie

Keith Richie — Fri, 20 Apr 2007 16:26:28 +0000

If you access the items via the SPList.Items[] collection, I believe it’s going to try to fetch a large number of items to cache locally to prevent multiple round trips to the database. Been ages since I did a SQL profile trace on it to confirm, but I worked with a lot of customers (And even experienced it myself) where subscripting the collection would cause a major delay, and you can see a noticible proc increase on your SQL server if your environment is just right . I think if you use a SPQuery object, it’s going to be a better solution, as the query that would be executed to gather the list items on the SQL server would be structured completely different. It’s one of those things I too would like to spend some time on, run SQL Profiler on, and document my findings. In fact, I may actually be getting to that in a couple of weeks as I plan to begin performance testing the new crawling engine I’ve written for DeliverPoint.

Still, you can never gaurantee that a third party web part may be tuned to work “Best” with this scenario, and these things can be very difficult to track down.

Since posting this, people are still telling me that it’s views, but it’s more than just views. It all depends on your backend hardware, your SQL server, etc, etc. but when it hits, it hits hard. I’d like to prove to myself that this problem is completely gone in MOSS, but as I note the official Microsoft guidance, I’d still recommend keeping them to ~2000 items per level just to be 100% sure.

By: Matt Smith

Matt Smith — Thu, 19 Apr 2007 22:11:31 +0000

Keith,

One thing I’m curious about is what if you never plan to enumerate the entire list? In other words, what if you were only to query the list for sets of items that would never even exceed 100 let alone 2000? Could we then put the documents in a flat list without issues? Have you ever tried this?

thx.

Matt

By: Keith Richie

Keith Richie — Wed, 21 Feb 2007 05:09:35 +0000

Are those 40,000 items in a single folder? If so, it’s going to hurt Because most of the load will be on the backend to enumerate and return those items. If they are in a single folder, that’s where you perf hit is going to be.

By: Piotr

Piotr — Wed, 21 Feb 2007 04:28:11 +0000

Keith,

what happens during a full crawl when the sitedata.asmx returns those lists with 40,000 items and is not so smart to apply a view that I have custom coded for the list?

Piotr