Table Creation and Initial Data Load
Imagine your organization has decided to gradually migrate away from your current primary database to an alternative technology.
Initially, you’ll use the new database only for real-time reporting. But over time, the alternative will become your primary database, although you may choose to retain the current one for legacy systems, or as a fall-back option.
How do you begin using heterogeneous replication technology to implement these requirements? How will you create the tables? What about the initial data load? And what if you have schema changes? None of this is easy.
To make matters worse, table creation and initial load isn’t necessarily a one-time step. Requirements can change, which means you’ll need an additional transformation. Or you might add tables that initially were outside of the scope of the project. Or you may uncover tables that are out of sync. What will you do?
Get full control over the changes between source and target
HVR automates the migration of schema/database changes made on the source to the replicated target.
With HVR you build real-time integration between databases in complex environments in a channel. The channel contains any transformations you want to implement and can be used to:
- Generate DDL on the target database
- Initially load data, automatically transforming source database data types into destination data types
- Perform real-time change data capture and data integration
- Provide the basis for data validation
Incremental changes are retrieved using non-intrusive log-based change data capture. Data is automatically compressed (5x – 10x compression is common) and optionally encrypted over the wire, both during the initial load and for real-time data integration.
- Ease of use
- Fast data movement between source and target
- Secure data transfer