Multiple projects

G

Gary M

For every release of our product we have multiple areas involved:
Requirements area, Development, QA, etc. Typically each area has it's own
project plan (2003) although each area has tasks dependent upon tasks in
other areas. We could look at having one plan but the issue is you can only
have one person editing at a time. The question is: would moving to storing
the data in SQL server or going to Project Server help this? I saw how you
can link tasks between project plans but am not sure how well this would
work between multiple .mpp files.

Any thoughts?

Thanks,
Gary
 
G

Gary M

Thanks,
I see a lot of discussion of project and project server but not much about
project and SQL Server. Are most people that are using Sql Server also
using Project server?

Also if SQL is the answer then from this perspective what does Project
server add to this. I see that it provides things such as web access and
portfolio roll up but is that all (I realize that is a lot but I am trying
to find as much value as possible). From a project manager perspective is
it worth adding Project Server into the mix or does Project Server provide
more value to upper management tracking all of the companies projects?

Thanks,
Gary
 
G

Gérard Ducouret

Hello Gary,

Project Server is the mandatory gateway between MS Project Pro and MS SQL
Server.
That solution is very efficient to manage a large resource pool shared by a
large number of project plans.
But each project plan can't be open more that once with Read/Write
permission, even when you work with Project server and SQL Server.

Gérard Ducouret
 
G

Gary M

Gérard,
Thanks and some more questions if you have the time:

1. If we do the master project/sub project then we should be okay? Each
area would update their project and we can get the "50,000 foot" view of the
data from the Master project.
2. Also, I need to clarify that I can't directly use SQL Server with MS
Project 2003. It seems the only interface to SQL Server (in MS Proj 2003) is
import or export. No direct access (reaffirming what you said).

Thanks Again,
Gary
 
G

Guest

-----Original Message-----
Gérard,
Thanks and some more questions if you have the time:

1. If we do the master project/sub project then we should be okay? Each
area would update their project and we can get the "50,000 foot" view of the
data from the Master project.
Click to expand...

Yes, but is can get very very slow depending on the number
of project to insert, their size and the number of
assignements per task...... but it theoritically works.
Nevertheless, time to open the consolidated plan can take
up to 10 real minutes if very large files are used



2. Also, I need to clarify that I can't directly use SQL Server with MS
Project 2003. It seems the only interface to SQL Server (in MS Proj 2003) is
import or export. No direct access (reaffirming what you said).
Click to expand...

Correct and uncorrect. The PDS method of Project Server
gives a method and instruction set to directly attack the
DB. But the DB model is so sophisticated I would only
attemps to read from it, not to write directly in
it....unless you perfectly understand the table structure
inside. Some companies (like mine LOL) specialise in
interaction between SQL and other company environments....

Olivier
 
G

Gary L. Chefetz [MVP]

Gary:

You most certainly can use SQL server to store project plans without Project
Server in the picture. Simply click the ODBC button in the save dialog and
point to a DSN that you've already created to talk to the database.
 
Top