Hi,

Cluster configuration or hot-standby configuration is not what 
distributed processing mean. Clusters improves scalability and high 
availability and hot-standby increases availability. Distributed 
(transaction) procesing means that a transaction may spread across 
several databases (2 phase commit protocol). SAPDB does not support XA 
interface and cannot be used within transaction monitors. But one can 
emulate this behavior (like JDBC does). Another case is replication 
availability. For now there is no simple, server built-in solution for 
this.

Bye
Janusz

> 
> Hi Nigel,
> 
> Thanks for the reply - I'm a bit confused though...
> 
> SAP's documentation certainly claims that is can run in both a cluster
> configuration and a hot-standby configuration (see
> http://www.sapdb.org/pdf/teched2002.pdf pg 23-25) and "Not only does 
SAP DB
> fit flexibly into multiprocessor systems or cluster configurations, 
it also
> exploits system advantages, such as high availability, without 
expensive
> integration. SAP DB's versatile architecture makes it the perfect 
choice
> for distributed IT infrastructures." (see
> http://www.sapdb.org/7.4/pdf/factsheet1101.pdf).
> 
> Then I also saw this in the mailing list regarding SAP NOT supporting
> distributed processing:
> http://listserv.sap.com/pipermail/sapdb.general/2003-June/038373.html.
> 
> Can anyone give a definitive answer on what and what is not supported 
by
> SAP when we try and go for an enterprise-wide solution?
> 
> Many thanks,
> 
> David
> 
> 
> 
> 
> 
> 
> "Nigel Campbell (DSL AK)" <[EMAIL PROTECTED]> on 25/08/2003 
10:00:40 PM
> 
> To:    "'[EMAIL PROTECTED]'" 
<[EMAIL PROTECTED]>,
>        "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> cc:
> Subject:    RE: Running SAP as Distributed Database
> 
> 
> You can make a standby server (the wiki at sapdb.2scale.net has
> some references to documents about this), although it's not designed
> to run in a cluster.  The loader utility would let you do soft
> replications between instances with a bit of basic scripting if you
> could live without the replication happening in realtime.
> 
> Nigel.
> 
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 26 August 2003 10:24 a.m.
> To: SAPDB General
> Subject: Running SAP as Distributed Database
> 
> 
> 
> Hi,
> 
> I have heard that SAP is designed to run fully as an entriprise 
database,
> ie distributed on different machines, all updating back to the main 
server.
> 
> Is this true?  Can someone point me in the right direction to do this?
> 
> Or is it hearsay?
> 
> Many thanks,
> 
> David
> 
> 
> 
> _______________________________________________
> sapdb.general mailing list
> [EMAIL PROTECTED]
>  http://listserv.sap.com/mailman/listinfo/sapdb.general
> 
> 
> 
> 
> 
> _______________________________________________
> sapdb.general mailing list
> [EMAIL PROTECTED]
> http://listserv.sap.com/mailman/listinfo/sapdb.general
> 
> 


_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to