SharePoint Use Cases

  • Home
  • About
  • Our Tools
  • Contact me
SharePoint

Versioning Hell – Part 1

Toni Frankola - July 8, 2008

One of the key features of SharePoint is versioning. But if not planned correctly versions can become your nightmare on a SharePoint project. During project planning phase perform requirements analysis on versions and once implemented educate end-users on how to use versioning correctly.

Versioning is a very good feature but Office documents can be huge so it is a good plan to limit the number of versions you want to keep in your document libraries.

Lesson 1 – Setting versioning limits

This lesson is very important, and, as a SharePoint consultant, you must know this by heart [:D]. It will also be useful for the following posts in this series.

You can restrict number of versions in following ways:
1) You can limit the number of major versions
2) You can limit a number of major version that will have minor versions
3) You CANNOT limit a number of minor versions to keep for a major version

versions1

Lesson 2 – Reaching version limit

When you hit your version limit the oldest version will be deleted. If major version limitation is set to 3, the following will happen when you publish version 5.0

versions2
Before
versions3
After

In next post I will try to explain the most common questions you will be asked about versioning by end-users on a SharePoint training.

Tags | versioning
 0
Share Now

Toni Frankola

Entrepreneur, IT consultant, speaker, blogger, and geek. Co-founder of syskit.com.

You Might Also Like

SharePoint

Comparing versions of a Word document

July 1, 2007
SharePoint

Versioning Hell – Part 2

July 14, 2008
SharePoint

How to: Display Check-in comments

November 3, 2009
Office 365, SharePoint, SharePoint 2013

Managing document library versioning settings with Governance Toolkit for Office 365

January 27, 2014

2 Responses

  • Eman October 3, 2008 at 12:36 pm

    Dear Toni

    There have been lots of discussions regarding document versioning in our department.

    I’ve heard that SharePoint keeps entire documents in past versions rather than just the delta, as done by some other versioning tools.

    Is that true? This can quickly consume disk space in a big company or department even if we limit the version tree as described in the blog.

  • Toni October 3, 2008 at 2:05 pm

    I think you have to correct information. Sharepoint stores the complete copy of each version into database. It was probably designed in such a way because old binary formats were hard break into deltas. I do not know if there is any improvements with Office 2007 formats.

    On a large implementation I would suggest limiting the number of versions to keep. If that will not be sufficient for you, you might wanna consider Enterprise Vault (http://www.symantec.com/business/enterprise-vault). It is a very good archiving software for Microsoft SharePoint and Exchange.

    If you have any questions please feel free to drop me a line,
    Toni

  • Comments are closed.

    Previous Post Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software
    Next Post Versioning Hell – Part 2

    Archives

    • December 2021 (1)
    • June 2021 (1)
    • January 2021 (1)
    • July 2019 (1)
    • June 2019 (2)
    • March 2019 (1)
    • February 2019 (3)
    • October 2018 (2)
    • August 2018 (2)
    • June 2018 (1)
    • April 2018 (1)
    • February 2018 (1)
    • January 2018 (1)
    • June 2017 (1)
    • April 2017 (1)
    • February 2017 (1)
    • November 2016 (2)
    • August 2016 (1)
    • July 2016 (2)
    • March 2016 (1)
    • February 2016 (2)
    • January 2016 (1)
    • November 2015 (2)
    • December 2014 (1)
    • November 2014 (2)
    • July 2014 (2)
    • June 2014 (2)
    • May 2014 (1)
    • April 2014 (2)
    • March 2014 (1)
    • February 2014 (4)
    • January 2014 (2)
    • December 2013 (1)
    • September 2013 (1)
    • July 2013 (1)
    • June 2013 (1)
    • May 2013 (1)
    • April 2013 (3)
    • February 2013 (1)
    • December 2012 (1)
    • November 2012 (1)
    • September 2012 (1)
    • August 2012 (1)
    • July 2012 (2)
    • June 2012 (4)
    • April 2012 (1)
    • February 2012 (1)
    • January 2012 (1)
    • November 2011 (2)
    • October 2011 (2)
    • September 2011 (2)
    • July 2011 (3)
    • May 2011 (2)
    • April 2011 (1)
    • March 2011 (4)
    • February 2011 (3)
    • January 2011 (4)
    • December 2010 (4)
    • November 2010 (3)
    • October 2010 (3)
    • September 2010 (4)
    • August 2010 (1)
    • July 2010 (4)
    • May 2010 (2)
    • April 2010 (2)
    • March 2010 (3)
    • January 2010 (2)
    • December 2009 (3)
    • November 2009 (5)
    • October 2009 (2)
    • August 2009 (7)
    • July 2009 (3)
    • June 2009 (4)
    • May 2009 (3)
    • April 2009 (5)
    • March 2009 (8)
    • February 2009 (5)
    • January 2009 (8)
    • December 2008 (9)
    • November 2008 (8)
    • October 2008 (7)
    • September 2008 (4)
    • August 2008 (6)
    • July 2008 (5)
    • June 2008 (3)
    • May 2008 (4)
    • April 2008 (6)
    • March 2008 (4)
    • February 2008 (3)
    • January 2008 (6)
    • December 2007 (1)
    • November 2007 (3)
    • October 2007 (3)
    • September 2007 (2)
    • August 2007 (1)
    • July 2007 (12)
    • June 2007 (2)
    • May 2007 (3)

    Connect Us

    All postings on this blog are provided “AS IS” with no warranties, and confer no rights. All entries in this blog are my opinion and don’t necessarily reflect the opinion of my employer.

    • Home
    • About
    • Our Tools
    • Contact me

    Copyright (c) Toni Frankola 2008. - 2019.