A separate group of IT personnel own the farm on which they are migrating from SharePoint 2007 to 2010. I have a production site that I have been building for the last two years. In particular, there is one list that has approximately 7,900 records already in the list. The list view threshold is set to the default of 5,000. I have done about three weeks of reading on anything Microsoft in effort to resolve this issue. I have attempted to execute every recommendation that I have extracted from this research. These executions include:

  1. creating a new list view complete with filter(s) to reduce the results to way less than 5,000. While the .aspx page will return the desired results, the minute I bring the list into a web part on a page and redirect the web part view to the new list view, that damnedable threshold error message is ALWAYS the result.

  2. creating an indexed column - I have gone through the list settings, click on the Indexed Columns-->create a new index-->set the primary index with no secondary-->clicked the create button. RESULT: that damnedable threshold error message.

  3. created a query that resulted in that damnedable threshold error message.

Since I don't own the farm, I cannot do anything at the farm level. The only other tool available to me is SharePoint Designer 2010.

Is there ANYone out there that can provide a real answer to this problem?

(I gotta tell ya Microsoft, I understand why you incorporated the threshold, but I think it is one of your dumber ideas if the error is thrown because the query has to sort through more than 5000 records. What is the point of having the ability to have a large list if everything one does throws that damnedable threshold error message???) Yes, I am MORE than frustrated!!!

  • Is it necessary to display large list? If not I would create views based on filter. Commented Sep 6, 2012 at 20:09
  • @MariaBurton the issue is not just about creating views, it is also about using them, and about using other list settings.
    – Christophe
    Commented Sep 7, 2012 at 1:29

3 Answers 3


You need to have higher permissions in order to create an Indexed Column on a list with more than 5000 items so you would have to ask the admins to create the indexed column for you. However, once the index is created and it is the first field in your filter, it should work for you. At least initially.

A better option would be to have the Farm Admins enable the 'Daily Time Window for Large Queries' to some off-peak time (i.e. 5pm-7pm). This effectively disables large list throttling for that web application during that window. Not only would this allow you to view the list as you did in SP2007, but it should also let you create those indexed columns as needed, without requiring an admin.

Incidentally, the videos at that link are a fantastic resource for understanding the various options available for handling large lists in SP2010.

  • I second Dave's suggestion on those videos. The best resource I have found that explains things. Here is another link that describes how it works: office.microsoft.com/en-us/sharepoint-server-help/… . Note that it is not enough to just create views and indexes. The View queries must be configured to query on the indexed columns first, so the order you specify your filtering is important. Alternatively, create some folders.
    – Brian
    Commented Sep 6, 2012 at 21:09


You are correct. Simply indexing columns and creating filters on a large list isn't enough. I learned that the hard way today. Regardless of how you filter a large list (e.g. SharePoint View, Web Part, Application Page), the very first filter MUST return a subset less than the threshold. You have to remember that the filters are done in order, not together at the same time.

My instance, I had an application page and used CAML to query my list.

My first filter was returning a result greater than the threshold, which threw the error.

I realized the problem and rearranged my query so the first filter returned the smallest subset.

And voila! No more issues.


Quick Workaround: Execute following powershell script on customer SharePoint server to disable throttling on list which causing this LVT issue.

$clientWeb = Get-SPWeb "Customer Site URL"
$list = $clientWeb.Lists[“List Name on Which Throttling Should Disabled”]
$list.EnableThrottling = $false

Caution: Please provide appropriate web site url and list name as mentioned above.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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