Forum Discussion
Max recommended doc library size ?
I know that site collections can be up to 1 Gig but also read that the site becomes bogged down if there are too many files or if the data volume is too large. What is the suggested max sux
In the on-premises world content database sizes used to be an issue. The main issue would be taking backups etc.
For this reason the database sizes aren't relevant in cloud. i.e. it's Microsoft's problem ;-)
Of course the more data there is the slower queries could become. However have you noticed Google and Bing getting any slower? not really. The reason for this is that the search indexes are clever enough to find relevant data faster than less relevant data.
The main issue now as jcgonzalezmartin mentioned is the 5000 item limit on lists.
- I see. Is that 5000 item limit currently on fasttrack or is the solution a ways off? I read that we can enable some automatic index where O365 creates a key index or some field that can be used to prevent lockup at 5000 items. Maybe I saw it here ... https://support.office.com/en-us/article/Manage-large-lists-and-libraries-in-Office-365-B4038448-EC0E-49B7-B853-679D3D8FB784
- If you are talking about SPO, a single site collection can have up to 25 TB of storage as long as you have this storage at your tenant...just remember that at your tenant you have a storage up to 1 TB + 500 MB x Number of Licensed users. In regards of document libraries, you can store millions of documents there...but you have to be very careful when working with views since you won't be able to return in a single view all the documents stored and you will need to do things such as indexing the list to overcome the famous 5000 items in a single view that by the way is going to be increased by Microsoft at some point
- Thank you. I am indeed talking about SPO via office 365 online. I am surprised to see 25T. Is there absolutely no noticeable degradation of performance when increasing the size of the database? I definitely remember someone saying there is s performance hit where the queries slow down, the views slow down, etc.
Perhaps a more theoretical question is this: is sharepoint the Microsoft alternative to Dropbox or is it really intended more for collaboration (eg real time editing, etc) than document storage and file sharing? There is no OneDrive which uses simple binary blobs for an entire organization, so the transition from our network drive to office365 storage seems like we are somewhat misusing SPO for our main intention.
Do others use SPO as an alternative to a net drive and how big have people gone without slowdowns?
