JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for GP-UK Archives


GP-UK Archives

GP-UK Archives


GP-UK@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

GP-UK Home

GP-UK Home

GP-UK  1998

GP-UK 1998

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

SQL Anywhere as an example of X400 being redundant

From:

[log in to unmask], [log in to unmask] (Adrian Midgley)

Reply-To:

[log in to unmask]

Date:

Wed, 17 Jun 1998 10:46:31 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (68 lines)

Ewan a while ago remarked that the receipted delivery of messages which
X400 gives is achievable by applications, and therefore X400 is not
necessary.

Part of my background research produced the example below.

Sounds a useful approach for laptops, branches, and other EMR
applications, does it not.
------------

SQL Anywhere has replication functionalilty built into it. One then
applies that functionality when creating a distributed database. See
below for key points that we used in a demonstration some while ago.
<name> can give you chapter and verse if you need it.

<name>

Replication Facilities
Sybase SQL Anywhere provides built-in facilities for data replication
between a consolidated (or master) database and one or more remote
databases. The consolidated database contains all the data to be
replicated. Remote databases may contain all the data or may contain
just some of the data. Replication is two way:

- changes made at the consolidated database are replicated to remote
databases; while
- changes made at a remote database are replicated to the consolidated
database and thence to other remote databases.

Remote databases can contain data tables that are not present in the
consolidated database so long as these are not involved in the
replication. 

Inter-System Data Transfer
Sybase SQL Anywhere exchanges data between databases using messages
that can be transferred either by e-mail, for databases that have no
direct connection, or by direct file transfer. Recognising that e-mail
systems do not guarantee that messages will reach their destination nor
arrive in the order they were sent, the database system incorporates
protocols to guarantee that all replication updates are received and
are applied in the correct order. 

Database Integrity
Sybase SQL Anywhere incorporates robust methods for ensuring the
integrity of the distributed database. For example:

The relational database management system (RDBMS) maintains a record of
the current status of replication from the master to all subscriber
databases. This enables the software program that initiates
inter-system data transfers to be written so that it will also generate
a log file to report their outcome. 

The RDBMS contains a “guaranteed transmission mechanism”. The
replication process is bi-directional so that a receipt is sent for
each data transfer, corrupt files are detected and failures are
automatically re-transmitted.

Also, by replicating portions of its internal transaction log the RDBMS
ensures that database transactions (additions, updates, deletions) are
replicated atomically, i.e. either a whole transaction is replicated or
none of it is replicated.

These features ensure database integrity throughout the distributed
system.


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

March 2024
October 2023
August 2023
June 2023
May 2023
February 2023
June 2022
October 2021
January 2021
October 2020
September 2020
August 2020
July 2020
June 2020
March 2020
January 2020
December 2019
September 2019
July 2019
June 2019
May 2019
March 2019
February 2019
January 2019
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
March 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998
1997
1996


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager