multiple instances of project server?

[Andy Novak]

In a real-world environment, does anyone recommend multiple instances
of project server for development, test, production, etc.?

If so, who many and which ones?

Thanks,
Andy Novak
University of North Texas
Computing & Information Technology Center

 

[Dale Howard [MVP]]

Andy --

Yes, it is not unusual to have several instances of Project Server. For
example, we frequenty work with companies where we install a production
instance and a training instance. The training instance is usually a full
working copy of the production instance. Some companies use a staging
instance for testing purposes, and a production instance. Other companies
will also add an archive instance for archiving completed projects.

How many you should create depends on the needs of your organization, as
there is no "right" answer to your question of "how many and which ones."
To create additional instances, you should using the EditSite 2003 tool
which is available for download from Microsoft at:

http://www.microsoft.com/downloads/...3e-54e1-40a9-9bb8-2dd293226b6f&DisplayLang=en

Hope this helps.

 

[Andy Novak]

Thanks Dale. Right now we are using the "classic" approach with the
application on one machine and the database on another. Would it be
safe to say you could put all 3 testing, training, and production
instances of the application on one box and all 3 databases on the
other box?

Andy

 

[Vadim Bogdanov]

Andy it's OK -
you might need to transfer configurations from one instance to another?

Check this out: http://make.bogdanov-associates.com/eng.asp?rubr_id=476

Regards,
Vadium

 

[Gary L. Chefetz \(MVP\)]

Andy:

You have to be careful about "development" instances. It depends on the
meaning of development is. If you're doing lots of custom code changes, you
don't want this sharing bits or servers with production.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-