Home | Sign in | English EN

  • Overview
  • Implementing spare replication
  • Specific features
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Stored procedures
A "spare" server is a target server in a unidirectional automatic replication. It is a form of backup almost in real time.
This server is accessible only in read-only mode (except for the automatic backup operation itself).
The advantage of a spare server is the simple implementation of the infrastructure. Compared to a replication, it is not necessary for the data file (table) to have an 8-byte auto ID item.
If necessary, the Spare server can switch to "non-Spare" mode to take over, for example, in the event of a disk crash on the main server.
It is a simple tool, offered along with the implementation of a replication and a cluster, to benefit from a backup server.
One or more spare servers can also be used to distribute a "read-only" load (e.g. product catalogs on multiple web servers).
Implementing spare replication
Spare replication can be implemented:
Specific features
The data on the spare server is read-only.
When an entire server is replicated in spare mode, the following elements are also replicated:
  • creation, modification or deletion of accounts,
  • automatic creation of accounts via Active Directory,
  • creation, modification or deletion of groups,
  • modification of rights,
  • creation or deletion of triggers,
  • creation, activation, deactivation, deletion of a scheduled procedure task,
  • creation, activation, deactivation, deletion of a scheduled optimization and materialized view calculation task.
  • The creation of a scheduled backup task is not replicated. But it can be created on the spare server.
  • A scheduled procedure task is not executed on the spare server.
  • Triggers are not executed on the spare server.
  • Integrity and secure password: All data files with integrity constraints must have the same password for the replication to take password-protected file integrity into account. Otherwise, the replication will not work.
Minimum version required
  • Version 25
This page is also available for…
Click [Add] to post a comment