| HOW IS HVR USED? |
The HVR has a proven track record in business situations where there is need for quick and reliable database replication. It is used in the following solutions:
Stand-by Database
A stand-by database can be configured to avoid downtime due to an emergency on the production server or due to planned downtime. If an emergency happens the application can be re-connected to the stand-by database. The stand-by database can also be used to avoid planned downtime, for example while rebuilding table indexes or while upgrading the DBMS. By switching over to the stand-by database HVR can avoid downtime during these operations.
Workload Distribution
HVR can provide a realtime feed into a data warehouse or a reporting database. Regular users will use the production database, whereas the reporting database will be used for reporting and analytical purposes. The target database for workload distribution could be the same DBMS as the production database, or it could be a different DBMS.
Bridge between Databases
HVR can provide a bridge between different databases. For example, between an internet database and the back office database. These data-models could be quite different, so HVR must consolidate and transform the data during replication.
Enterprise Replication
Bus As an enterprise replication bus, HVR is used as strategic middleware which connects all the business processes.
|
