List Size Limit within SharePoint 2010

364010 pts.
Tags:
Sharepoint 2010
What’s the list size limit within SharePoint 2010?

This question is from the Microsoft Live Chat which took place on June 1st.



Software/Hardware used:
SharePoint 2010

Answer Wiki

Thanks. We'll let you know when a new response is added.

There is capacity planning guidance–very detailed guidance!–on TechNet. Capacity is really about performance–there are very few hard-wired limits–and performance is based on usage and content.

Here are the software boundaries and capacity planning thresholds and limits. http://technet.microsoft.com/en-us/library/cc262787.aspx. Short answer: SharePoint 2010 scales further (way further) and more flexibly than ever before

Some guidelines include: 100GB per site collection, 200GB per content database (unless you have single-site document repositories, in which case TBs are supported), 300 content DBs per web app, 250,000 Web sites per site collection (2,000 under any one site), and tens of millions of items/documents per list/library. But again, these are HIGHLY dependent upon hardware, topology, usage, etc.

There is no hard limit on the number of items in a list. A good rule of thumb is 5,000. 5,000 are the new 2,000 :)

Oh sorry–LIST size limit is tens of millions of items. However you can manage the performance of lists (Spencer’s note about 5,000) in several ways. It’s all about query (and view)… THOSE are the limits… the list itself can have tens of millions of items.

The feature we’re talking about is List Throttling, which allows an admin to control the impact of large lists on the rest of the farm.

<i>This question was answered by Spencer Harbar, Enterprise Architect at Microsoft and Dan Holme, Consultant and Trainer, Intellium.</i>

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Walkabout

    Let's say I have a need to have several lists sized between 500 and 250,000 records.  Are 250,000 to large for loading the table into cache?  For testing (and because in the system currently my list size is limited) I have reduced the size by breaking the list size down in to yearly tables (i.e. F8609_2014, F8609_2013 etc.) by the years of the data content. 

    Usage will involve an Access Front-End and a SharePoint back-end.  Anywhere from 10-15 (max) users at a time, who can query for record(s) that need to be updated.  Usually less and no more than a query result of 20 records max to find the one(s) for updating to load the forms from list/tables by query for updating that after update is completed on the form will be updated on the list/table by update queries run by buttons on the form.

    The list/tables have 66 fields; 28 text, 21 double, 2 memo, 2 date/time, 3 long integer.  

    There are list and aggregate reports in the Access front-end (requiring more records to be queried at the same time) as well - but they will not be used frequently, only occasionally for review and analysis.

    Remember:

    1) Users will not be querying the same records.

    2) Users will be updating only 1 record at a time.

    3) List and aggregate reports will only be run occasionally.

    Here is what I need to know;

    Will the loading of the Access cache from the SharePoint to the Access Front-end links take too long?  What will be the breaking point of reasonable efficiency for the users? Currently using the yearly list/tables it only takes about from 2-30 seconds to load the yearly test tables.  

    Will this small volume of users be enough to hurt the speed of adding, retrieving and updating records?

    Are there any other (or better) features to accommodate this volume of data for such an Access/Sharepoint Services arrangement? 

    I know more testing is the best way to understand the thresholds of effectiveness for this SharePoint/Access services database.  But any insight, comments or experiences you have to lead me in the best direction for an effective solution is appreciated! 

    Thanks,

    Walkabout   

     

    10 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

Share this item with your network:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following