Practical scalability in CMS

Couldn’t resist in posting this…

One colleague came to me today and described a problem (and a resolution):

SharePoint. over 6 million documents inside. a “few” GB in size. what to do?

The problem was, the client needed to move this content volume from one installation to another. The dump&load tools which is from Microsoft seems to take each content item and shove it to the dump. With probably a lot of overhead in each get next, fetch, load, save, close… Sometimes crashing… eh.. that’s life

What to do? Get the content out of SharePoint ! Now, please. (awating flames on this…)

Round 2:

SharePoint. Gimme a “count” of all items in a document library… “Out of Memory”. whtf?!

Why? The CMS (lol) fetches each item and “counts” it. Like using your fingers to count. 

What to do? Beats me.. Ask some moooore money to improve it through development? Lol

Rant done. Flame away!


Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s