M
milhouse
Hello all,
We have implemented Project Server with over 4000 users in the resource pool.
As this is an extremely large and varied organization we have allowed users
to retain local custom fields so that they can flavour their project
information as they require. We are currently experiencing horrible server
saving performance for project files that have local custom fields. File
saves and using Build Team from Enterprise on the Project Schedules is
excruciatingly slow.
Does the way in which Project Server saves a file change if the schedule has
local custom fields? The degradation in performance is astonishing with file
saves now taking in excess of 5-8 minutes for files with these custom fields.
Does anyone know of ways to optimize this? We have made the Enterprise
Global as small as possible with only a few views and tables in order to
increase the performance, but now, having done that, we are experiencing the
same, almost reciprocal problem, now that we have allowed users to use local
custom fields.
I haven't really gotten any information out of MS on this issue and would
really appreciate any insight or even an explanation on why this is happening.
Thanks,
Scot
We have implemented Project Server with over 4000 users in the resource pool.
As this is an extremely large and varied organization we have allowed users
to retain local custom fields so that they can flavour their project
information as they require. We are currently experiencing horrible server
saving performance for project files that have local custom fields. File
saves and using Build Team from Enterprise on the Project Schedules is
excruciatingly slow.
Does the way in which Project Server saves a file change if the schedule has
local custom fields? The degradation in performance is astonishing with file
saves now taking in excess of 5-8 minutes for files with these custom fields.
Does anyone know of ways to optimize this? We have made the Enterprise
Global as small as possible with only a few views and tables in order to
increase the performance, but now, having done that, we are experiencing the
same, almost reciprocal problem, now that we have allowed users to use local
custom fields.
I haven't really gotten any information out of MS on this issue and would
really appreciate any insight or even an explanation on why this is happening.
Thanks,
Scot