question

sns1 avatar image
0 Votes"
sns1 asked JoyZ commented

Contentdatabase took 6 hours to mount in 2016


Contentdatabase took 6 hours to mount in 2016 envirounment

we have migrated 2010 to 2013 one database which holds one site, but when we mount back in 2016 it took 6 hours where it tool it less than 30 minutes in 2013

why it happened?

size for that site collection in that db is 86 GB, that db holds one site, is size causing the delay?
what could be other reasons? Please clarify

office-sharepoint-server-administration
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

You should open a support case with Microsoft as this is going to be very specific to your scenario and will often require logs during the mount process. We can give you generalizations, such as slow performing SQL server (i.e. someone used a 4K clusters on the volume containing MDF/LDF which will cause slower performance, though usually only by ~30%), poor network connectivity between SharePoint and SQL, hundreds or thousands of subwebs, etc. but nothing definitive.

0 Votes 0 ·

1 Answer

JoyZ avatar image
0 Votes"
JoyZ answered JoyZ commented

Hi @sns1,

The maximum size of the content database is between 200 GB and 4 TB, size may not be the issue.

Make sure the memory and CPU of your SharePoint 2016 server and SQL server are Okey.

In addition, before you mount a content database, we suggest you Test-SPContentDatabase cmdlet to check if there is any issue.


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.


· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

82244-testoutput1.jpg82149-testoutput2.jpgHi Wang,

Please find the attached output of test-spcontetndatabase
yes CPU and RAM looks good.
Please suggest further. I see under site collection settings site upgrade status showing 0 errors.
but y it took 6 hours to mount? when size does not matter for this db?


0 Votes 0 ·
testoutput1.jpg (281.4 KiB)
testoutput2.jpg (323.4 KiB)

Hi @sns1,

All the missing features are listed above, and seem to have nothing to do with performance.

Check ULS logs to find if you have slow connectivity to SQL Server.

In addition, it's hard to say why this takes 6 hours, you could create a new web application, attach another content database to check if this will takes you long time.

0 Votes 0 ·