Product Overview
Jump to: Topologies Supported / FAQs / Use Cases / Platforms Supported
Efficiently Integrate High Volumes of Data Between Your Different Platforms
You need a complete set of capabilities to get up and running, whether you plan to use data replication for real-time reporting, big data analytics, or ongoing cloud integration. HVR is a complete data integration solution that performs change data capture at scale.
With HVR you can:
Move Large Volumes of Data Fast in Complex Environments- Enable Bi, Uni, and Multi-Directional Data Movement
- Simplify data management with a single point of control
- Deploy for many use cases
HVR has proven its stability and robustness. It keeps on running and running with minimal maintenance effort. HVR guarantees secure delivery of all our data.
– Director of IT, PostNL
Download the data sheet for HVR latest release: HVR 5.2 Data Lake Release.
HVR is the only solution to provide all relevant real-time data integration capabilities in a single unified environment. Our solution enables you to perform real-time replication and reliable, high-volume data synchronization between databases and file systems..
Rich Platform Support
With HVR, you can move your data between the most commonly used relational databases, file systems, data-warehouses, data lakes, cloud systems, and more.
 |  |  |  |
All-in-one Box
Everything you need for real-time data replication is included with HVR:
- Table Creation and Initial Load
- Change Data Capture
- Data Validation and Repair
- Automatic Reporting and Monitoring
This all-in-one solution comes in a less than 100MB download. Not only is it a small download, but is easy to manage and use. You can control all of these features through a Graphical User Interface. (GUI)
It’s pretty simple to use and it mostly gets the job done without fuss. –Analyst Programmer, Kent Police U.K.
Real-Time Data Replication Topologies
HVR supports a variety of topologies while providing you confidence in your data movement
With HVR, you get the ability to not only move data from one source system to another but also the ability to move data bi-directionally and multi-directionally while maintaining efficiency and accuracy. Watch the video to see how HVR solves for use cases such as migrations, active/active, data lake consolidation, real-time reporting and more.
Features such as collision detection, data validation, and reporting and monitoring give you assurance in moving high volumes of data in your complex environments.
Topologies Supported
FAQs
- Can HVR replicate data from a single source to multiple targets?
- Yes, in fact that is one of the advantages of HVR’s architecture. HVR can capture from a single Oracle instance, queue the captured changes on the hub, and then integrate those changes to as many targets as needed. HVR does not have any limitation on the number of targets.
- Can HVR replicate data from a multiple source to a single target?
- Yes, HVR can be configured to capture data from many sources and then replicate to a single target. Many data warehousing solutions require data to be collected from any number of sources to be either combined into a single target warehouse database or into separate target schemas. Some applications and data are designed so that there will not be any conflicts on primary key constraints. If that is not the case for your scenario, then HVR offers you the option to add extra columns and set to values stored in the metadata to make sure you don’t have any conflicting primary keys.
- Does my source and target layouts need to have the same structure and layout?
- No, tables do not need to have the same layout. You can instruct HVR to ignore certain columns or populate extra columns during replication. Column values can also be changed through transformations as well as enriched with the results querying other tables, either on the source or the target. HVR also makes additional transactional metadata values to be available to be mapped to columns, such as source timestamps or transaction identifiers.
- To minimize any impact to our network, can we compress the change data before it sent over the network?
- Yes, in fact HVR already compresses the database by default before sending over the network using an internal algorithm which achieves very high compression rates. The impressive compression ratio reduces impact on your corporate network while using little overhead on the source.
- When instantiating the target database, does the user have to pre-create the target tables, or can HVR help with that?
- The initial load of the target tables takes place by running an HVR Refresh operation. The Refresh can create all the target tables if they don’t already exists. The target tables are created based on the DDL of the source tables in conjunction with any column re-mapping that the user has configured in the replication channel.
- Can HVR convert all insert, update, and delete operations and insert them into a time-based journal or history table?
- Yes, HVR Integrate provides a feature known as TimeKey which converts all changes (inserts, updates, and deletes) into inserts into separate tables. HVR will log both the before and after image for update operations, the after image for insert operations, and the before image for delete operations. HVR also logs additional transaction metadata to provide more time based details for every row replicated. HVR will also automatically create the tables with the preferred structure for timekey integration.
Common Customer Use Cases
| Industry | Company Name | Use Case | Data Platforms |
|---|---|---|---|
| Services | Epsilon | Consolidation of Data in to a Data Warehouse | Oracle Production Database and SQL Server Data Warehouse |
| Transportationl/Aviation | Luftansa/LIDO Flight Planning | Geographic Distribution, Real-Time Reporting | Oracle, Ingres |
| Logistics | PostNL | Cloud Migration | Oracle, SQL Server |
| Government | United States Coast Guard | Real-Time Reporting, High Availability | Oracle, Ingres |
| Financial Services | Investment Services Firm | Geographic Replication, Real-Time Reporting | Oracle to Oracle |