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

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

How to implement a SharePoint "Change Management Process"

Not so much from the technical point of view, SharePoint Change Management is the process of monitoring and controlling changes within a SharePoint project. By managing the implementation of change, you can: • Reduce the impact of changes to the SharePoint project • Identify new issues and risks as a result of changes raised • Ensure that changes do not affect the SharePoint project's ability to achieve its desired objectives • Control the cost of change within the SharePoint project Change Management is comprised of the following processes: Step 1: Identify Change: The first step in the change process is to identify the need for change. Any team member can suggest a change to the SharePoint project, if he or she believes it is needed to keep the SharePoint project producing deliverables to the customer's specified requirements. After identifying a need for change, the team member records relevant information on a Change Request Form (commonly called a CRF), describing the chan
2 comments
Read more

Zambia's first K2 BlackPoint roll-out

Reporting to you live from Code|Influence... My colleague and I have been managing our organization's SharePoint infrastructure for some time now and we have just rolled out the first K2 BlackPoint in the country, intended mostly for SharePoint workflow developments.
8 comments
Read more