PDS Delay

[A.Karim]

Most of the API Methods like ProjectsStatus and ProjectCodeValues can not
specify parameters “specific fieldsâ€. So, by calling one of them, the
returning XML text is very huge. And the PDS would be very slow.

I thought of building a method. But this requires calling a (USER MADE)
stored procedure which reads from a (USER MADE) view, built by joining some
tables.

This means direct access to the database (just like SQL statements) which is
not recommended by Microsoft.

So, how can I minimize the delay of processing and being on the save side as
what Microsoft recommend.

Thanks in Advanced,

 

[Ed Morrison]

Provided you are not concerned with Project Server security, I would do a
direct read against the database. This is much more efficient as it returns
only what you ask for.

Remember that Microsoft recommends using the PDS which is based on SOAP.
SOAP is not the Microsoft recommended protocol anymore. Its Web Services.

 

[A.Karim]

would you please provide me with some resources or references regarding using
web services to access the Project Server database.

 

[Ed Morrison]

Project Server 2003 does not have built in web services, so your primary
options are the PDS or straight SQL. I don't want you to get too hung up on
using "what Microsoft recommends" since that technology is becoming
obsolete. Instead, use the best access method for today.

--
Ed Morrison
msProjectExperts
"We wrote the books on Project Server"
http://www.msprojectexperts.com
FAQ - http://www.projectserverexperts.com

 

[Cory K. Walker]

You aren't making a proper comparison here.

PDS is a Web Services interface that encapsulates XML using SOAP over HTTP.
This is the recommended interface by Microsoft.

SOAP is the industry standard for delivering XML payloads and is endorsed by
Microsoft in conjunction with Web services.

 

[Cory K. Walker]

That statement is incorrect.

The PDS is a built-in Web services interface for Project Server 2003.

 

[Cory K. Walker]

Allow me challenge your requirements:

+ Do you have a requirement that says an update or set of updates must occur
within a given time frame?

I know things may seem slow when you use the PDS, but the reason we use XML
and Web services is not for performance, but because we understand the
structure of the information better.

I'd strongly agree with other posts and suggest to try to solve your problem
using the PDS. Operating directly on the SQL database is considered a
higher-risk activity. Therefore, you need to weigh the following tradeoffs:

+ The PDS is a low-risk, well-understand Web services API. In theory, using
it will make your application less prone to errors, so less maintenance is
needed.

+ The Project Server database is high-risk, complex, and not-well-understood
mess of tables. Yes, it is documented, but not as well as the PDS. Do you
think the risk of accessing the database directly just to get a little more
performance is worth it?