Carsten, this is one of our "long term" planning items. Because of shifting priorities this item has been postponed several times.
Regards, Juergen -----Original Message----- From: Carsten Kuckuk [mailto:[EMAIL PROTECTED] Sent: Montag, 2. Juni 2003 12:04 To: [EMAIL PROTECTED] Cc: Primsch, Juergen Subject: RE: Look, SAP is abandoning SAPDB - it failed to take off Juergen, Thank you for this explanation. I can understand why you wanted to get rid of the distributed database code. Did you still leave some of it in place so that XA transaction coordination could some day be implemented? Carsten Message: 2 From: "Primsch, Juergen" <[EMAIL PROTECTED]> To: "'Carsten Kuckuk'" <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: RE: Look, SAP is abandoning SAPDB - it failed to take off Date: Mon, 2 Jun 2003 09:37:10 +0200 Hi Carsten, it was the decision of the development, that moved to SAP, to drop all activity, which was related to distributed database management. At this point of time we faced severe performance problems caused by the approach to handle distributed update transactions on replicated data. This was caused by the synchronization of locks held on different nodes within a distributed database. On the other hand we had to focus on object management (liveCache). So we choose to decrease comlexity in our db kernel. And looking back this was a good decision (and I don't see any other systems having success with a full distributed approach according to Dates rules). Regards, Juergen Primsch _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
