Managing content database of large sizes

Question

Hi all,

We have one scenario where our SharePoint 2016 Content Database has grown up to 4 TB in size.

As per business rule, we cannot move the large site collections to new content DB so we have to stick with one single content DB.

We want to check if

1. We split content DB over multiple disks, will it break any SharePoint component?
2. Is there any official documentation to handle the 4 TB database in SharePoint?
3. If we split the content DB into multiple disks, will it impact the Microsoft support? (or is it something that Microsoft does not recommend for SharePoint content DB)?
4. Will the SharePoint be down during the database split?

Answer 1

Hi @Amit Dimri ,

Per my research, there is no available documentation to handle the 4 TB database and i did't find any useful article about splitting content database over multiple disks. Normally, we recommend you to create new content databases and move site collections to the new content databases. But this solution is not suitable to you. So i would suggest you open a ticket with Microsoft for furthur help.

---

If an Answer is helpful, please click "Accept Answer" and upvote it.

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.