MS Project files in Database

[Riko Wichmann]

Dear all,

I'm currently building a structure of MS project files for a large
project consisting of several sub-projects:

The master project file has only the sub-project files inserted. The
actual planning is going to be on the sub-project level done by
sub-project leaders. In total, there are 3 hiearchy levels built up from
the sub-project files. In addition, I set-up a resource file for the
entire project which is used by all sub-project.

Currently the hierachy of MS Project files is just stored in a folder
structure on a file system. However, I read about the same approach but
storing all files in a project database (not the server, just using
standard). I'm just in the beginning of setting this structure up, but
so far, i didn't see any disadvantage of NOT using a database ...

1) What are the advantages/disadvantages of using a database/filesystem?
2) Do I lose functionality (except not being able to access the data of
the project files through the database) when just use a filesystem?

Any advise would be very helpful ...

Cheers,

Riko

 

[Rod Gill]

Hi using a db - Pros:

Database is in one place so people less likely to move files or rename them
so corrupting the links and potentially a file
Can generate reports across all projects directly from db

Cons:
Slower to open/save
Can't take files away on a laptop so easily.

Be sure to keep regular backups, links between files (sub-projects and
resource pools) can easily be corrupted by people moving or renaming files
without disconnecting from the resource pool or master project first.

I often advocate keeping all projects separate and consolidating weekly (no
links so you get a copy of all data) and do reporting on the new
consolidation. This makes sure there are no corruptions, allows moving and
renaming files without risk of corruption and still enables resource
reporting and consolidation of all tasks. The snapshot also acts as a weekly
audit of progress.

--
For VBA posts, please use the public.project.developer group.
For any version of Project use public.project
For any version of Project Server use public. project.server

Rod Gill
Project MVP
For Microsoft Project companion projects, best practices and Project VBA
development services
visit www.project-systems.co.nz/
Email rodg AT project-systems DOT co DOT nz

 

[Mike Smith]

You can still keep all the mpp files on a shared drive and
use a tool like Housatonic Web/Server to publish them
online to the team members. Look at
www.projectviewercentral.com-they have an online demo that
will probably give you more inside info