SharePoint 2016 content database size increase

Jian Hong Lek 0 Reputation points


I have a customer, which one of their SharePoint 2016 site is getting full of around 700GB. May I know what is the best approach of increasing the datastore or does SharePoint 2016 site support secondary datastore such as .ndf system? as further increasing the same datastore will be hard to managed.

SharePoint Server
SharePoint Server
A family of Microsoft on-premises document management and storage systems.
2,060 questions
SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
11,566 questions
SharePoint Server Management
SharePoint Server Management
SharePoint Server: A family of Microsoft on-premises document management and storage systems.Management: The act or process of organizing, handling, directing or controlling something.
2,701 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Olaf Helper 36,001 Reputation points

    Database increasement happens, when you insert additional data.

    Stopp adding data and database increasing stops (... sorry for that joke:-)

    secondary datastore such as .ndf system

    The database file group/files structure is for client as SharePoint completely intransparent, they aren't aware of. So yes, you can add additional database files.

    1 person found this answer helpful.
    0 comments No comments

  2. Yanli Jiang - MSFT 18,581 Reputation points Microsoft Vendor

    Hi @Jian Hong Lek ,

    SharePoint 2016 supports increasing the size of a content database up to 4 TB, provided that certain requirements are met, such as disk subsystem performance and high availability plans. However, it is strongly recommended to limit the size of content databases to 200 GB, except when specific usage scenarios and conditions support larger sizes. In this case, the customer's SharePoint site is already at 700 GB, which is well beyond the recommended limit.

    To address this, it is recommended to split the content database into multiple databases, rather than increasing the size of the existing database. This can be done by moving site collections to different databases. It is suggested that for ease of backup and restore, individual site collections within a content database be limited to 100 GB.

    It is also recommended to proactively manage the growth of data and log files by pre-growing all data and log files to their expected final size, enabling autogrowth, and setting the database autogrowth value to a fixed number of megabytes instead of a percentage.

    For your references:

    Hope this is helpful.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.