SharePoint Content Database Sizing
        Posted  
        
            by Sahil Malik
        on Win Smarts
        
        See other posts from Win Smarts
        
            or by Sahil Malik
        
        
        
        Published on Fri, 01 Nov 2013 06:36:15 GMT
        Indexed on 
            2013/11/01
            16:10 UTC
        
        
        Read the original article
        Hit count: 482
        
sharepoint
| SharePoint, WCF and Azure Trainings: more information | 
SharePoint stores majority of its content in SQL Server databases. Many of these databases are concerned with the overall configuration of the system, or managed services support. However, a majority of these databases are those that accept uploaded content, or collaborative content. These databases need to be sized with various factors in mind, such as, Ability to backup/restore the content quickly, thereby allowing for quicker SLAs and isolation in event of database failure. SharePoint as a system avoids SQL transactions in many instances. It does so to avoid locks, but does so at the cost of resultant orphan data or possible data corruption. Larger databases are known to have more orphan items than smaller ones. Also smaller databases keep the problems isolated. As a result, it is very important for any project to estimate content database base sizing estimation. This is especially important in collaborative document centric projects. Not doing this upfront planning can
        
        
© Win Smarts or respective owner