Are you sure that API is no charge. I got a different message from Primavera Australia and my company brough 500 users licenses but still they want to charge us for $20,000 for a licese of API. Any PAR can clarify this
SDK login is slow, maybe due to the amount of PROJECT codes, resource codes you have etc.
i have use SDK and API, SDK do gets slow when lots of global codes is loaded.
SDK is not that bad, because you can use Microsoft technology to write your codes, any there is ways to improve the speed dramtically. (like multi threading, caching of the data).
lots more.
API is ok too, but only works with JAVA, if you have skills in Java, then go for API,
it has more features and speed, You will need to purchase an extra license.
Member for
20 years 11 months
Member for20 years11 months
Submitted by Shirish Borkar on Wed, 2004-11-24 07:17
Have you heard about Primavera Integration Server APIs. API does all those things which SDK can do. It is faster than SDK and more robust. Suggest you to use API instead of SDK.
Member for
22 years 11 months
Member for22 years11 months
Submitted by Bernard Ertl on Thu, 2003-05-29 14:08
We are using ADO to interface with the Primavera SDK for P3e and P3e/c. The performance is quite acceptable on our end. Connection and log-in takes roughly 5-15 seconds on my old 400Mhz P-II with Win 98 and a slow HD (when P3e is not already running).
It is quite reasonable to expect that connecting via the SDK will produce a performance hit over a direct connection. The SDK is adding another layer of processing. However, the SDK also offers some important functions and safety mechanisms to maintain the integrity of the data. I would not recommend altering the back-end data directly without the SDK.
Two minutes seems an awful long time to wait for a connection and log-in. I would guess that there is some issue in your case that needs examining.
BTW, in general, using ADO to manipulate a back-end database will never be as quick as using COM to manipulate data directly. Ie. you should not expect to automate P3e / P3e/c with the same speed that you could with P3. Its just the nature of the design structures.
Member for
22 years 10 monthsRE: Anyone Using SDK?
Refer to here for more on this subject. Good luck!
Member for
22 years 8 monthsRE: Anyone Using SDK?
Mario
Are you sure that API is no charge. I got a different message from Primavera Australia and my company brough 500 users licenses but still they want to charge us for $20,000 for a licese of API. Any PAR can clarify this
Alex
Member for
22 years 8 monthsRE: Anyone Using SDK?
Vu
Good to C you back in action.
SDK is the basic free of charge integration tool for P3e
API of course is "better" because it cost you money to actually purchase it so it better be "Perform better".
Alex
Member for
21 years 1 monthRE: Anyone Using SDK?
SDK login is slow, maybe due to the amount of PROJECT codes, resource codes you have etc.
i have use SDK and API, SDK do gets slow when lots of global codes is loaded.
SDK is not that bad, because you can use Microsoft technology to write your codes, any there is ways to improve the speed dramtically. (like multi threading, caching of the data).
lots more.
API is ok too, but only works with JAVA, if you have skills in Java, then go for API,
it has more features and speed, You will need to purchase an extra license.
Member for
20 years 11 monthsRE: Anyone Using SDK?
Hi,
Have you heard about Primavera Integration Server APIs. API does all those things which SDK can do. It is faster than SDK and more robust. Suggest you to use API instead of SDK.
Member for
22 years 11 monthsRE: Anyone Using SDK?
We are using ADO to interface with the Primavera SDK for P3e and P3e/c. The performance is quite acceptable on our end. Connection and log-in takes roughly 5-15 seconds on my old 400Mhz P-II with Win 98 and a slow HD (when P3e is not already running).
It is quite reasonable to expect that connecting via the SDK will produce a performance hit over a direct connection. The SDK is adding another layer of processing. However, the SDK also offers some important functions and safety mechanisms to maintain the integrity of the data. I would not recommend altering the back-end data directly without the SDK.
Two minutes seems an awful long time to wait for a connection and log-in. I would guess that there is some issue in your case that needs examining.
BTW, in general, using ADO to manipulate a back-end database will never be as quick as using COM to manipulate data directly. Ie. you should not expect to automate P3e / P3e/c with the same speed that you could with P3. Its just the nature of the design structures.
Bernard Ertl
InterPlan Systems Inc. - Project Management Software, Project Planning Software