'Save As' with Resource Pool

[SGM]

Quick sanity check - In our situation, we want to link up
a resource pool to a project that is versioned multiple
times per day. Should we follow a standard practice of
breaking the link from the resource pool to the previous
version after each 'Save As'?

I'm thinking that we may encounter some performance
problems if we leave all those links to the resource pool
out there indefinitely?

Any other related words of wisdom? Thanks!

 

[John]

SGM,
The only potential problem I see is if the file "Save As" is to a
different location each time. Then it depends on whether you need to
preserve the pool link to an older version. If you need to keep previous
versions as backup, then the link to the pool should remain. However, if
you are simply using "Save As" to prevent file growth (a good idea),
then the "Save As" would be to the same path and there is no impact on
the resource pool link (i.e. no additional links are created).

Others may have their own opinion.

Hope this helps.
John

 

[SGM]

Thanks John - this helps...The other reason I was
wondering about removing the links was a potential
performance hit, if the Pool is trying to maintain
references to multiple versions of the project schedule.

 

[JulieS]

Hi SGM,
I would add a word of caution. I have seen Project
maintain the resource pools links to both the "old"
version of the project as well as the "save as version"
leading to false resource overallocations.
I suggest a routine audit of the resource pool file to
see what files it thinks it is supplying resources to.
Hope this helps.
Julie