Predecessors in Proj Serv 2007 database

[Andy S]

Does anyone know where the predecessors (or successors, depending on
how you look at it) are stored in the Project Server 2007 databases?
I assumed there would be an obvious column in the DRAFT database,
MSP_TASKS table. However, nothing in there seems to be indicate which
task is a successor to another task.

Thanks!
Andy

 

[Jonathan Sofer]

Hey Andy,

Both the Draft and the Published database have the predecessor and successor
relationships stored in MSP_LINKS, you will need to join it with MSP_TASKS
to get the full data you are looking for.

Jonathan Sofer

 

[Chris Boyd]

Hey,

Can you provide more details on what you are trying to do? Are you trying to
build reports? Develope code against Project Server? There may be better ways
to get and set this information then going directly to the database, which is
not support. You can end up degrading the performance of the server, or have
your application broken after an update is applied.
--
Chris Boyd
MS Project
Program Manager

Blog: http://blogs.msdn.com/project_programmability/

 

[Bryant Likes]

[snip]

There may be better ways
to get and set this information then going directly to the database, which
is
not support. You can end up degrading the performance of the server, or
have
your application broken after an update is applied.

Querying the database is not supported? I thought only updating the database
was not supported? Do you just mean that MS will not offer you support for
querying the database?

Just wanted to double check that statement since this is something I'm
currently working on and I don't want to put us into a non-supported
scenario.

Thanks!

 

[Rod Gill]

Yes,

That's why no schema is published. Only reading from reporting db is
supported for which a schema can be found in the Project 2007 SDK
downloadable for free from MSDN.

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com

[snip]

There may be better ways
to get and set this information then going directly to the database,
which is
not support. You can end up degrading the performance of the server, or
have
your application broken after an update is applied.

Querying the database is not supported? I thought only updating the
database was not supported? Do you just mean that MS will not offer you
support for querying the database?

Just wanted to double check that statement since this is something I'm
currently working on and I don't want to put us into a non-supported
scenario.

Thanks!

 

[Andy S]

I am attempting to build a report directly from the database. We have
two PMs with access to the same schedule, and each wants to know what
the other has changed. Therefore, I will take a snapshot of the
database in the morning, and then compare it with a snapshot of the
database in the evening. All fields that have changed will be put
into a report and sent to the PMs.