A
Andrea Padovano
I' ve migrated a customer from Project 2000 (storage on file system) to
Professional and Project Server 2003 (storage in DB).
In this migration, I had not particular problem. But database access is very
slow, compared with file system access (both in 2000 and 2003). About 1 to 5
time (for example : saving a master project is about one minute in DB and 20
second in file system).
In this case, I have about 20 project (about 100 to 300 task each). We have
several enterprise fields (4 activity fields and 4 resource fields). An
Enterprise Resource Pool, and several macro.
Projects are inserted in a master file (publishid and saved in DB) in order
to level and analyze resources (about 50 resources).
Slow access is both via http, both via odbc. It is slow both open a master
project, both a single project. Saving, too, is slow.
Any idea about slow access problems ? Anyhing related to enterprise fields ?
I' ve other customers with DB and performance are good. And I' m not able to
find specificity in this case.
Thank you.
Bye.
Professional and Project Server 2003 (storage in DB).
In this migration, I had not particular problem. But database access is very
slow, compared with file system access (both in 2000 and 2003). About 1 to 5
time (for example : saving a master project is about one minute in DB and 20
second in file system).
In this case, I have about 20 project (about 100 to 300 task each). We have
several enterprise fields (4 activity fields and 4 resource fields). An
Enterprise Resource Pool, and several macro.
Projects are inserted in a master file (publishid and saved in DB) in order
to level and analyze resources (about 50 resources).
Slow access is both via http, both via odbc. It is slow both open a master
project, both a single project. Saving, too, is slow.
Any idea about slow access problems ? Anyhing related to enterprise fields ?
I' ve other customers with DB and performance are good. And I' m not able to
find specificity in this case.
Thank you.
Bye.