[Prior Post in Series]

The Temenos T24 application can make use of many of the high availability features that come with SQL Server 2008 R2 Enterprise and Data Center editions.  In part 1 of this series about high availability options for Temenos T24, we took a look at Failover Clustering.  In part 2 we reviewed Database Mirroring.  In part 3 we took a look at Log Shipping and finally in this post, we'll be discuss Replication.

Replication is a set of processes for copying and distributing data (and objects) from one database to another and then synchronizing to maintain consistency.  The Temenos T24 application supports both server-to-server transactional replication and peer-to-peer replication.  With these methods, there is a window of a few seconds to a few minutes where the transactions committed on the primary site are not yet committed on the DR site. 

 

The above diagram shows a server-to-server transaction replication topology

(image source: http://technet.microsoft.com/en-us/library/ms151706(SQL.90).aspx )

The above diagram shows a peer-to-peer replication topology

(image source: http://technet.microsoft.com/en-us/library/ms151196.aspx )

NOTE: Transactional replication is recommended for maintaining a near real-time copy of the T24 database for reporting purposes. For reducing the data volume of the reporting database and network utilization between the servers, it is also possible to replicate only a subset of the T24 tables that are relevant for reporting. T24 system tables can be omitted from replication as they do not contain business data. Temenos provides a list of system tables that do not need to be replicated.

Please click here for more information from TechNet on SQL Server 2008 - Replication

Stay tuned for future blog posts on other High Availability options for Temenos T24

Please review the Best Practices for Running TEMENOS T24 on Microsoft SQL Server and Windows Server whitepaper for more information.