<< Click to Display Table of Contents >> Navigation:  Technical Informations > Database - Dual Database Partial Cross Synchronisation > Scope of the method

The method aims to address most prevalent issues that can affect users after the outage of one of the database servers resulting in a partial desynchronisation, such as:

Items created during failover to secondary database do not appear when reconnected to primary database server.

Some items are only visible on some workstations when not all clients have failed over to secondary database server.

 

The method however has some limitations:

•It may generate some orphan entries albeit minimal if the database is properly maintained.

•It will NOT resynchronise tables outside of the selected crucial asset tables (T_ITEM, T_EDIT, T_RTF).

•It will NOT resynchronise item metadata changes (and by extension item status)

•It will NOT resynchronise media files.

 

The method is not a replacement for a high availability solution to keep databases completely in synch.

Organisations seeking such a result should use a different architecture and application connection method than “Double ODBC”.