hi,

 would like to know what are the  pros and  cons of content databases  of size  > 200 GB.

in my application its going to be > 1 TB of data/documents loaded into the content DB.

so how can i plan this? , since MSDN says that, if the content db size crosses 200 GB,its  difficult to perform the backup  operations. 

1) is there any other cons regarding the size, if my content  db size reaches  1 TB  /  2 TB? 

2) what will happen if i use the same content  db ,  having 1 TB of data , will it affect my  document retrieval in my custom

web part?

am  using custom view/custom list view web part in order to display the document names/links on a  page.

highly appreciate the help!

• Edited by SaMolPP Friday, February 07, 2014 6:23 AM

it's better to stick to best practice , try to limit your Database to be less than 200 GB as it will take more time for backup and restore 

if you have a huge files you might need to use  Remote Blob storage solution 

There are some scaling issues with very large databases. Item level permissions for example can hit performance and they are shared within the database. That means that even if they make up a small fraction of your site collection the absolute size could grow to the point of impacting performance.

You've also got increased time for maintenance processes, not just backup and recovery but also the daily indexing, statistics and  your manually scheduled consistency checks.

As for your custom web part, the scaling issues you're more likely to hit are around list sizes, which isn't directly related to the size of the content database.

Alex outlined this well. 

There is no pro to a database that large.  If you can I would highly recommend splitting out your content into more manageable sizes.