second instance on same server pair

[Guest]

Are their any known issues with installing a second instace (second
database, WSS, etc.) of Project Server 2003 on the same small-scale server
farm (1 DB, one FE)?

John Willard
Sr. IT Architect
VA Dept of Transportation

 

[Gary L. Chefetz \(MVP\)]

Only if your small-scale server is too small to handle the load.

--

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

-

 

[Earl Lewis]

John,

We're running three separate instances (all using one instance of SQL server with different dbs) on a single machine. It works fine for us.

Earl
Are their any known issues with installing a second instace (second
database, WSS, etc.) of Project Server 2003 on the same small-scale server
farm (1 DB, one FE)?

John Willard
Sr. IT Architect
VA Dept of Transportation

 

[Lars Hammarberg]

You could actually run multiple instances of Project agains the same WSS
server if you stagger the offset for the web projects id - i.e.: wproj_id
in the msp_web_projects table.
When publishing a project to pwa, the WSS site will be named after the
WPROJ_ID for that particular project - by default starting on 101 and
onwards. If you set the offset of that field (it's an automatically
incremented number) to 10001 in the second instance of projectserver, you'll
have nothing to worry about for the next 9900 projects...
The one thing you'll have to take into consideration is that the WSS Shared
Documents page will be available to all instances as this page is not linked
to the project id - this is in some of the scenarios I'm working in a bonus,
in others, it could be a problem and requires a separate WSS server.