separate database for Project Server and WSS

[NC71]

I am implementing a 2 server enviroment for my WSS 3.0 and Project Server
2003. I have a database server and an application server. I installed WSS
3.0 on my App server and its own database instance on the Database server. I
am now going to install Project server 2003. I was going to install it in
its own database instance on the database server. But I am wondering if this
setup will cause problems with the integration. Can I have a separate
database instance for each application? I wanted to keep them separate in
case we use WSS 3.0 for document libraries at a later time. Any information
would be appreciated.

 

[Ben Howard]

Hi,
1st things first, WSS3.0 and Project Server 2003 are incompatablie.
Project Server 2003 only works with WSS2.0. So, lets assume that you are
going to install PS2007 instead. In this case, the database instance peice
won't cause you an issue, it'll work technically.

However, I'm not sure why you think you need to do it, if as you say you use
WSS later for document libraries. In this instance, you would create another
WSS site and the docs will be stored in the same content db (it'll scale to
thousands of docs...). If you want another content DB, create another SSP to
host the new sites - each SSP gets it's own content DB.

 

[NC71]

Thank you. Now I need to see if we can upgrade to Project Server 2007,
because I want to use WSS 3.0.

 

[Christophe Fiessinger [MSFT]]

Check out the migration guide here (includes a recently published migration
whitepaper): http://technet.microsoft.com/en-us/library/cc303388.aspx