J
Jack Kohn
We are in the learning/testing phase with Project 2002 Pro/Server. I
need to do some capacity planning for production deployment.
We are considering installing Project Server on an existing IIS server
that's used for development. It's an IBM Netfinity x342 with a single
P-III at 1.26 GHz. and ~ 1.2 GB of RAM.
Will we regret doing this? I have read a number of posts about slow
performance. If Project turns out to be a dog, we certainly don't want
to be dragging down an existing server with it. (Although at least it
would be a development server.)
Has anyone else gone this route, sharing their Project Server with
other apps/developers, or are most people dedicating an IIS server to
Project?
Also - has anyone found/developed a good rule of thumb for SQL Server
requirements? We also plan to use one of our existing SQL Servers for
Project data. (Most of these are dual-processor P-III's with up to 4GB
RAM.) I am still hunting for guidelines on how much disk space I
should request from our DBA's. Some posts lead me to believe that
"undocumented features" (?) may grow our SQL tables by 10GB or more.
We expect to have about 50 Project Pro users and another 20 Web Access
users. Our project portfolio is roughly 60 "large" projects and 140
"small" projects.
Any advice appreciated in advance. Thanks!
-jmk
Jack Kohn
need to do some capacity planning for production deployment.
We are considering installing Project Server on an existing IIS server
that's used for development. It's an IBM Netfinity x342 with a single
P-III at 1.26 GHz. and ~ 1.2 GB of RAM.
Will we regret doing this? I have read a number of posts about slow
performance. If Project turns out to be a dog, we certainly don't want
to be dragging down an existing server with it. (Although at least it
would be a development server.)
Has anyone else gone this route, sharing their Project Server with
other apps/developers, or are most people dedicating an IIS server to
Project?
Also - has anyone found/developed a good rule of thumb for SQL Server
requirements? We also plan to use one of our existing SQL Servers for
Project data. (Most of these are dual-processor P-III's with up to 4GB
RAM.) I am still hunting for guidelines on how much disk space I
should request from our DBA's. Some posts lead me to believe that
"undocumented features" (?) may grow our SQL tables by 10GB or more.
We expect to have about 50 Project Pro users and another 20 Web Access
users. Our project portfolio is roughly 60 "large" projects and 140
"small" projects.
Any advice appreciated in advance. Thanks!
-jmk
Jack Kohn