4

Do we have any limitation for documents( pdfs , excels , msword ) in media library in sitecore 8.1. Actually We are planning to upload around 60,000 documents in media library.

As I know the purpose of CMS is that we can full have control on content as per our need but sure not sure about this scenario

7

While Sitecore would be able to store that many documents, There are some things you may want to consider:

Maintenance

With the Search API in the content editor maintenance will be easier than it used to be, but still managing that amount of documents will not be simple.

e.g there is no way to bulk edit documents, or bulk move documents around. Sure you could use Sitecore PowerShell Extentions for that, but its still not the easiest.

Database Size

Another potential problem would be the size of the master and web DB's once you have that amount of documents in. This will make backup/restoring and general DB maintenance take longer, disk requirements will go up etc..

Publishing

Because you are on 8.1 the new publishing service is not available, so if you ever need to publish large parts of the media library, or worst case need to republish the entire site, this will take an extremely long time. Publishing media items is slower than normal items anyway because of the blob data.

With those considerations, if I were looking at storing that many documents and the budget allowed for it, I would look at a dedicated Digital Asset Management system (DAM) - Sitecore have DAM for Sitecore and there are others around. A dedicated DAM will solve a number of the above issues as they are built to manage that many documents.

If you have no budget for that, then Sitecore will be able to handle it, but plan the content tree carefully so you have the min amount of maintenance to do once the documents are there.

  • thanks richard for your response on this but as you mentioned new publishing service is not available what service you are talking about... – Sukhjeevan Apr 26 '17 at 19:00
  • @Sukhi Sitecore Publishing Service is a new way of publishing that uses an external .net core process rather than running in the website process. – Richard Seal Apr 26 '17 at 19:40
  • that's correct...I also have concern about Database size/Publishing and if budge allow I will definitely go for DAM other wise finally we will be ended up having lots of docs in media library node. Any suggestion on this I mean how should we plan keeping docs in media library in efficient way ( If business says NO for DAM ) – Sukhjeevan Apr 27 '17 at 4:44
1

I believe that is not the number but the size that will drive your decision. Having a lot of blobs in your database means that you have to multiply this by 2 or 3 (master, web, public? database) + backups. Disk size consumption and restore time may be an issue.

  • yeah that's why looks like DAM implementation is best option – Sukhjeevan Apr 28 '17 at 13:28

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.