You are designing a SharePoint 2010 application that stores data in a list named Base List. This list contains
25,000 records. A view named View List filters data on a column named Create Date. The Create Date column is
of type Date and Time. The View List view requires too much processing time when displaying Base List data.
Your design needs to improve the performance of the View List view when it displays the Base List data.
Which approach should you recommend?
A.
Enable the Display items in batches of the specified size property in the Item Limit option of View List.
B.
Set the Group By option of View List to group by the Create Date column.
C.
Add a column index to Base List based on the Create Date column.
D.
Change the Create Date column type to Date Only.
Filtered views with column indexes (and other operations) create database queries that identify a subset of columns and rows and return this subset to your computer.
To help improve the performance of a large list or library, you can index up to 20 columns. In general, an index on a column enables you to quickly find the rows you want based on the values in that column, even when working with millions of items. When you combine indexes with filtered views, you can quickly retrieve the items you want.
It is important to consider the following when you create and use indexed columns. Each additional column index consumes extra resources in the database and adds some overhead to every operation to maintain the index. Therefore, you should add indexes only to columns that will be used actively for filtering in views on the list or library. It’s a good idea to look at all the views and see which columns are used most commonly across different views for filtering to help choose the right columns to be indexed. Note that any column that you define to have a unique value requires an index.
http://office.microsoft.com/en-001/sharepoint-foundation-help/manage-lists-and-libraries-with-many-items-HA010377496.aspx#_Toc264017708