Recommendation for archiving projects / 5000 limit
Considering the use of Project Online only (not project server 2013), how would you recommend getting around the 5,000 project count limit ? I need to make sure my organization can have a record of projects that completed, and some information about them like the name, major dates, and other high level information like planned start/planned finish, actual start/actual finish, planned hours, actual hours, etc... along with timesheet data about who tracked how much time to what tasks when.... all that should hopefully be maintained. Is that a possible scenario today? Or do we just hope that by the time we hit 5000 projects that Microsoft has raised, or removed that limit... or introduced archiving? I suppose an alternate solution is to export all the information we'd like to report on to another reporting service, but that kind of defeats the purpose to having one tool / one pane of glass for the sol
May 26th, 2015 4:39pm

Hi Ian,

I would suggest to write down a procedure for archiving projects. It could be for example as following:

  1. in a first step, you flag the completed projects as "completed' through a project custom field, you lock and unpublish all tasks, you add the project into an "archived" security category.
  2. in a second step, you could delete year-1 "archived" projects from the draft/publish DB and only keep them in the archived DB.
  3. in a third step, you could totally delete year-2 projects from the archived DB and keep a local copy on a shared repository.

Keeping a report is another solution.

Free Windows Admin Tool Kit Click here and download it now
May 27th, 2015 3:32am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics