This is my opinion and others may take a different view on this.
You want to use the full functionality of MSPS2003? Don't use MS Project
2002 to access the MSPS2003SP1 server. Upgrade all your PMs to MS Project
2003 Professional SP1. (Oh, don't go to SP2 on the server - it's way to way
to buggy.)
Get (at least) two brand new clean servers and load IIS on one and SQL with
Analysis Services on the other. I'd say at least two is because I have no
idea what your resources-per-task, tasks-per-projects and number-of-projects
are.
Load WSS and load MSPS2003 (with SP1). If you never have done the install,
you do it at least half a dozen times before your get half the gotcha's out
of the way.
Huge assumptions: Let's say you successfully loaded WSS and MSPS2003 SP1 and
let's say you are up to speed in MSPS 2003. This is not meant to be
derrogatory thing here. I'm -warning- you 2003 has it's own load of gotcha's
and bugs and workarounds (as you can see from the forum questions here) you
need to be aware of...
BACK UP AN IMAGE NOW! Or if you know SQL, just backup the "ProjectServer"
database. If everything goes sour, you can just restore to this point.
Create your Enterprise Global with the appropriate Enterprise fields you
want to use. (Easy to say, this will take you a week of design time and
everyone would want to fiddle with the contents, so good luck...)
BACK UP AN IMAGE NOW! Yes, save it here again.
Type in your Enterprise resources into the Resource Pool. If you are saying
2002 is buggy, don't cut and paste! Invisible control characters and other
garbage can toss your resource pool into a mess quicker than anything else...
Don't use any special charaters! Okay, you can use underscore "_", but stay
away from eveything else. (I'm being overly cautious here.)
BACK UP AN IMAGE NOW! Yes, save it here again. You'll really thank
yourself for doing this after you have to blow away your practice for the
tenth time.
Next, save off all open projects on your old 2002 system. I assume (bad
assumption) these projects are not corrupt. If they are corrupt in 2002,
they will be imported as corrupt in 2003. Open MSP2003 and do a "Tools",
"Enterprise Options", "Import Project to Enterprise". This is also tough the
first time you do it. Just match your 'local' resources to the 'enterprise'
resources and you'll be fine. Again, experiment.
*****
Yes, you can have two or more databases on Project Server. Use the
"EditSite" tool (download from microsoft.com) to set them up. You can log
onto PWA to the production data or to the "test" or "archive" data. If I go
into "EditSite" here, it would be way too long... (Just search MSDN on
'EditSite'...)
Good luck.
