Master Project

[Mike Mahoney]

All

I am considering following architecture:

Top Level Master (x1)
--Programme Master (x8)
----Programme Summary (x5)
---------Programme Detail (x5)

Each detail level plan could contain 1800 rows. Therefore top level
master could contain 8x5x1800 (64000 rows)

Has anyone worked with this volume and hierarchy in Project Server
2007?
Is it doable?
How robust is it?
What are performance issues?
Other thoughts (Are you mad?)

Thanks

Mike

 

[Jack Dahlgren]

64K rows is a lot, especially if you have many assignments and custom fields.
I'd probably just use some links to create the top level plan. That would
keep the numbers down. Hardware, networking and memory are the limiting
factors here. Why not try building a schedule like that (just take the
project and copy it many times until you have 64000 tasks)? See if it is
workable in your environment and with your hardware.

-Jack Dahlgren

 

[Mike Mahoney]

64K rows is a lot, especially if you have many assignments and custom fields.
I'd probably just use some links to create the top level plan. That would
keep the numbers down. Hardware, networking and memory are the limiting
factors here. Why not try building a schedule like that (just take the
project and copy it many times until you have 64000 tasks)? See if it is
workable in your environment and with your hardware.

-Jack Dahlgren









- Show quoted text -

Hi Jack

I have worked with multi-level master project but not such large
numbers. There is a sensitivity around working with master projects
(so generally keep fingers crossed when I do so). So I was curious
whether anyone was doing this on a large scale. Meanwhile I have been
discussing requirement with client challenging the benefit of such a
large schedule and it seems to be diminishing.

regards

Mike