List view threshold SharePoint
Go To SharePoint Admin Site > Select Web application > General Settings >Resource Throttling>
For threshold , best practice lime 5000, lookup support 8 after patch 12,
1:The default threshold for general users is 5000 items.
To increase this threshold, you need to modify the Resource Throttling properties of the web application. In Central Administration, select Manage Web Applications and then select the web application you wish to modify.
2:On the Resource Throttling >increase the List View Threshold value
**3:**SharePoint 2013 works the same as 2010 in terms of list view threshold: you can use folders and/orviews filtered on indexed columns to access items in a list/library with more than 5000 of items.
**4:**You can index up to 20 fields in your SharePoint Lists in Libraries in SharePoint 2013. If you have a list that has more than 5,000 items you CANNOT filter (using List Views or Web Services) on fields that have not been indexed.
5:After you index your fields, you can then create custom List Views where you filter on those indexed fields. You can even filter on “begins with” which allows you to do some more dynamic views.
List view lookup threshold |
8 join operations per query |
Threshold |
Specifies the maximum number of joins allowed per query, such as those based on lookup, person/group, or workflow status columns. If the query uses more than eight joins, the operation is blocked. This does not apply to single item operations. When using the maximal view via the object model (by not specifying any view fields), SharePoint will return up to the first eight lookups. |
A Farm Administrator can disable Throttling on a list-by-list basis.
using PowerShell to disable list throttling
$web = Get-SPWeb "http://your site"
** $list = $web.Lists["library name"]**
** $list.EnableThrottling = $false**
** $list.Update()**
--Or-----
$web = Get-SPWeb "http://site/to/web/w/list "
$list = $web.Lists[“LIST_NAME”]
$list.EnableThrottling = $false
To validate the Throttling settings
$list.IsThrottled
--------------------------
To re-enable throttling on a list
$list.EnableThrottling = $true
$list.Update()
What Is Indexing?
SharePoint enables you to index columns in a list. This is conceptually similar to indexing columns in a database table; however, in the case of SharePoint lists data, the index is maintained by SharePoint instead of SQL Server.
Indexing columns in a list can substantially improve the performance of various query operations, such as queries that use the indexed column, join operations, and ordering operations such as sorting. In any list, you can either index a single column or define a composite index on two columns. Composite indexes can enable you to speed up queries across related values.
A list instance supports a maximum of 20 indices. Some SharePoint features require indices and cannot be enabled on a list where there is no index slot remaining. You should choose your indexed columns carefully to maximize query performance while avoiding unnecessary overhead
How Does Indexing Affect Throttling?
The list view threshold does not apply simply to the number of results returned by your query. Instead, it restricts the numbers of database rows that can be accessed in order to complete execution of the query at the row level in the content database. For example, suppose you are working with a list that contains 10,000 items. If you were to build a query that returns the first 100 items sorted by the ID field, the query would execute without issue because the ID column is always indexed. However, if you were to build a query that returns the first 100 items sorted by a non-indexed Title field, the query would have to scan all 10,000 rows in the content database in order to determine the sort order by title before returning the first 100 items. Because of this, the query would be throttled, and rightly so—this is a resource-intensive operation.
In this case, you could avoid the issue by indexing the Title field. This would enable SharePoint to determine the top 100 items sorted by title from the index without scanning all 10,000 list items in the database. The same concepts that apply to sort operations also apply to where clauses and join predicates in list queries. Careful use of column indexing can mitigate many large list performance issues and help you to avoid query throttling limits.
Note: Throttling is enabled for a good reason. Disabling throttling can cause performance problems. If you need to disable throttling for a specific list, ( recommend moving the site collection containing the list to a dedicated content database)