Timeline for Large content database
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 11, 2012 at 16:50 | comment | added | Anders Rask | The 4TB limit is only for very specific scenarios where IOPS and other specs are within specs specified i guidance. Very specific scenarios | |
| Jan 10, 2012 at 16:18 | comment | added | Rob Wilson | I should qualify that I'm speaking from experience not from the official guidance. The guidance has actually been updated to 4TB, but I would not personally recommend that any of my clients. I would not want to be the person who migrated that content database to SharePoint vNext. blogs.msdn.com/b/pandrew/archive/2011/07/08/… Also, if a site collection is greater than 100 GB, then it should be the only site collection in the content db: sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=988. | |
| Jan 10, 2012 at 6:49 | comment | added | Anders Rask | The official guidance regarding content db is 200 (and site collection same as content db). Ofcourse this is by no means an exact number, but that is an appropriate size with regards for time it takes to backup/restore, do B2B and especially V2V patching/upgrades, etc. | |
| Jan 10, 2012 at 5:31 | history | answered | Rob Wilson | CC BY-SA 3.0 |