PS 2007 : Project Archive

[Jonathan H]

Hello,

I know there have been many questions about archiving of projects in PS
2007, so apologies for another.

We've been using PS 2007 for about a year now and desperately need to
archive off projects. Two places I know we can't apply views to filter out
the old information is:
- The Open dialogue in Project Professional 2007.
- The Resource Utilisation view - it shows every project the resource has
been involved in and slows this page down too much.
There may be others.

The only solution I can imagine (and I'm _definitely_ open to other options)
is to create another project server instance and move completed projects to
this. That way I can still report.

- Is this what other people have done?
- What have you done about licensing as it seems crazy to require two
production licenses because the product doesn't do a very good job (or any
job at all) of archival?
- How easy is it to come up with a process to move projects and workspaces?
Have you been able to turn it into a 'one-click' operation (or close)?

This is longer than your average post, so many thanks for making it all the
way through.

Jonathan

 

[Ben Howard]

Hi Jonathan,
You say you need to archive them off but still want to report on them, is
this for analysis/comparision within a financial year or just for adhoc
information.

If it's for comparison, then I expect you are using the olap cube for this,
why not create a single OLAP cube showing all the old projects, and then get
build the current OLAP cube in the normal way. You'll then need to use some
other tools to view both OLAP cubes at once, or maybe bring the resultant
data together via SRS.

If it's for ad-hoc query, I would save the project plan to an MPP file and
store it on the project workspace for future reference, or take all the
relevant files and store on a DVD.

Another instance on the same server will not require additional licences, so
you could do an STSADM export of the site an import to another site, and
import the project, but it will require a duplication of Enterprise codes,
calendars, resources etc so it alot of work (or use the playbooks but they'll
need to be kept in sync)