Download the Sybase Replication Server System Tables Diagram pdf below

Content Copyright:Sybase,Inc

Download the Sybase Replication Server Administration guide volume 2 pdf file below

http://infocenter.sybase.com/help/topic/com.sybase.dc32518_1500/pdf/rsadmin_vol_2.pdf

Download the Sybase Replication Server Administration guide volume 1 pdf file below.

http://infocenter.sybase.com/help/topic/com.sybase.dc32511_1500/pdf/rsadmin_vol_1.pdf

Download the sybase replication server 15.0 installation guide for unix below

http://infocenter.sybase.com/help/topic/com.sybase.dc32237_1500/pdf/rsunix_install.pdf

Download the simple diagram illustrating sybase replication server environment below.

Sybase Replication server

Sybase Replication Server supports the enterprise data management environment by replicating and synchronizing
Sybase ASE, Oracle, Microsoft SQL Server, and IBM DB2 UDB database transactions. It provides high performance,
secured, and guaranteed delivery of data across the enterprise, addressing:

• Data Movement, Distribution, Synchronization and Migration
• Real-Time Reporting
• Disaster Recovery

Sybase Replication server Key Capabilities:

• High performance data distribution and consolidation
• Bi-directional synchronization across heterogeneous data sources
• Centralized administration of complex deployments
• Flexible data translations
• Distributed architecture with guaranteed delivery

Database Replication for Heterogeneous Environments

Source Databases Target Databases

Sybase ASE Sybase ASE
...

Both SQL Remote and Replication Server perform replication. SQL Remote was originally part of the Adaptive Server Anywhere tool kit and is intended for intermittent replication. (The classic example is that of a salesman connecting on a daily basis to upload sales and download new prices and inventory.) Replication Server is intended for near real-time replication scenarios.

Basic Components of Replication Server

Primary Dataserver

The source of data where client applications enter/delete and modify data. As mentioned before, this need not be ASE, it can be Microsoft SQL Server, Oracle, DB2, Informix. (I know that I should get a complete list.)

Replication Agent/Log Transfer Manager

Log Transfer Manager (LTM) is a separate program/process which reads transaction log from the source server and transfers them to the replication server for further processing. With ASE 11.5, this has become part of ASE and is now called the Replication Agent. However, you still need to use an LTM for non-ASE sources. I imagine there is a version of LTM for each kind of source (DB2, Informix, Oracle etc). When replication is active, you see one connection per each replicated database in the source dataserver (sp_who).

Replication Server (s)

The replication server is an Open Server/Open Client application. The server part receives...

Move data from one source to another.
Move only a subset of data from source to destination. So, you can ‘subscribe’ to a subset of data, or a subset of the columns, in the source table, e.g. select * from clients where state = ‘NY’
Manipulation/transformation of data when moving from source to destination. E.g. it can map data from a data-type in DB2 to an equivalent in Sybase.
Provide a warm-standby system. Can be incorporated with Open Switch to provide a fairly seamless fail-over environment.
Merge data from several source databases into one destination database (could be for a warehouse type environment for example).
Move data through a complicated network down to branch offices, say, only sending the relevant data to each branch.

Basic Working of Replication Server

PDS : Primary Data Server
PDB : Primary Data Base

RDS : Replicated Data Server
RDB : Replicated Data Base

PRS : Primary Replication Server
RRS : Replicated Replication Server

RSSD : Replication System Database

1. RepAgent reads the record from transation log of the PDB for the tables which are marked for replication.

2. Logs into the PRS and write transactions in inbound queue of PDB in stable device.

3. Holds Data in inbound queue , untill it recieves commit.

4. Uses subscription information in its RSSD to decide what to do with the each transaction, after the commit:

i Discards the rans if there is no subscription.
ii Writes the transaction to the out bound queue if there are subscription.

5. Writes commited trans only in outbound queue according to subscription.

6. Sends transactions to their destination, it depends upone two things
...