Skip to main content

Open Source #SharePoint File Clean-Up Tool

Hello SharePoint Community. Don't we just love sharing code sometimes? Well I figured this might help someone somewhere in the community. First off, some basic house keeping.
  • Are you still running #Microsoft #SharePoint Server 2010?
  • Are you looking at migrating/upgrading to a more recent version of SharePoint but you would like to first clean up your environment and potentially reduce the size of your content databases?
  • Did you activate version history on some of your document libraries?
  • Did you forget to set the maximum limit of versions to retain on some of your documents libraries?
  • Do you wonder why some document libraries have grown so much in size and yet they don't have a lot of documents stored in them?

If you answered yes to any of the above questions, then this tool might be useful for you.
I've decided to open source a tool I created sometime back that would clean up your SharePoint 2010 stored file's version history. Feel free to download it on GitHub here. 

To give you a bit more information of what the tool does. This is a tool for cleaning up version history that has span out of control and resulted in large size document libraries. SharePoint 2010 had no shredded storage, therefore, each version retained the full document size. Shredded storage was only introduced in SharePoint 2013. The tool is a combination of #CSharp and #PowerShell. I packaged the solution as a WSP, deploy-able to the SharePoint Farm and the clean up happens under a #SharePointTimerJob, activated as a farm feature while the parameters like how many versions to retain or whether a site collection should be skipped for clean up is activated as a site collection feature.

In a situation where you are looking to upgrade your SharePoint farm, some might say, "Well since shredded storage is in SharePoint 2013 on-wards, then I wont need this tool", while others will say "Wait a minute, if I move my large sized document libraries, shredded storage in SharePoint 2013 wont magically shrink them now will it?"

If you are interested, head over to the #GitHub location where I have written down a step-by-step deployment guide and download the tool. As the tool is open source, I will great appreciate any feedback that you may have, including the negative ones ;)
I will also be making open source a SharePoint Library #Migration tool soon. Look out for it.

#HappySharePointCoding
Labels:

Comments

Post a Comment

Popular posts from this blog

SharePoint: How to create a custom action to open Word Documents using "Edit in Microsoft Word".

Imagine you have a SharePoint custom search webpart, and on your search results, you return word documents, you will obviously want to at times be able to open them in your MS Word client program for editing. So basically, depending on your office client installed on your local machine, there are 2 different approaches that can be made for Office 2003 and Office 2007/10, using the same function " editDocumentWithProgID2 ". For Office 2003: - If your document libraries versioning settings have got "Require Check out" ticked, then you will first want to check out the document using: onclick ="CheckoutviaXmlhttp(‘{SiteURL}’, ‘{DocumentDownloadURL}’)" - Then to open the document, you use: onclick =" return editDocumentWithProgID2(‘ {DocumentDownloadURL} ’, ”, ‘SharePoint.OpenDocuments’, ’1′,’ {SiteURL} ’, ’0′);" href ="#" - and now combining the above 2 actions into one clickable action: onclick ="CheckoutviaXmlhttp(‘ {SiteURL} ’, ‘ {...
2 comments
Read more

How to document your SharePoint Projects.

Here are the essential documents you need to complete… Initiation Business Case: To justify the financial investment in your SharePoint Project, you need to write a Business Case. It lists the costs and benefits, so everyone knows what the return on investment will be. Feasibility Study: Before you kick-off your SharePoint Project, you need to determine whether your project is feasible, using a Feasibility Study. SharePoint Project Charter: You then need to document the objectives, scope, team, timeframes and deliverables in a SharePoint Project Charter. Planning SharePoint Project Plan: You need to create a Project Plan listing all of the tasks required to undertake your SharePoint Project from start to finish. Every task must be scheduled, so you know what needs to be done and when. Resource Plan: Next, you need to plan your resources by documenting the money, equipment and materials needed for your SharePoint Project. Quality Plan: You then need to set quality targets, so that the S...
4 comments
Read more

Zambia's first Helpdesk System on SharePoint

For my 25th birthday today 3rd March, 2009, allow me to present to you another first of its kind in Zambia. Yes we have done it again, having been Project manager, I present to you Zambia's first Helpdesk System which Masialeti and I have developed on Microsoft Office SharePoint Server 2007. The system also implements SharePoint designer workflows, Infopath forms, SharePoint document library and sends email notifications to the relevant personnel. When a user logs in a call, the user automatically receives a mail from the system, telling them that their call has been received and is being attended to, IT section will also receive a notification and the helpdesk manager will assign the call to the right IT guy who will also automatically receive a mail notification from the system. When the call is resolved, the user again automatically gets notified by the system with a mail giving them description of the problem they logged and also how it has been resolved. The user also has an ...
7 comments
Read more