The premise for this blog is an to attempt to give you, the DBA, a visual on the ease of implementing HVR. With the DBA as a deciding factor in choosing a software to solve their real-time data replication needs. Here is a question a DBA may consider asking the replication software vendor:

  • What is the Level of Effort in implementing your real-time data replication software?

Why is this question important?  Well, it’s you who’s going to be stuck with the implementation of whatever replication software is decided upon, you the DBA and your fellow DBA cohorts. To the point, implementation: HVR S was built with implementation in mind. Even while your source systems are active, HVR can be up and running within a few steps. Minimizing the level of effort to implement a replication software that gives you in one implementation, the following HVR functions/components:

1. Instantiating/Initial load – HVR Refresh will build your target tables (DDL) followed with data.

2. Replication – HVR Software’s Change Data Capture.

3. Validation – HVR Software will prove your data is sync.

  • NOTE: The above three points are not separate. You truly need all three for a solid replication solution. Now let’s break this down in the form of an implementation plan coupled with a level of effort plan. Tip: the below can be copied and pasted into your Project Plan:

1. Prepping your source systems to accept HVR. Quick start guide provided to both active and trial customers. NOTE: This includes creating HVR OS user and HVRHUB db user. 5 min per source – 3 min per targets

2. Installing HVR Software 3 min per node (per node is if applicable)

3. Configure replication using the HVR GUI

  1. Connecting to your HVR HUB (schema or db)
  2. Defining HVR Location
  3. Creating HVR Channels
  4. Creating HVR Groups
  5. Select your tables for replication.
  6. Start HVR Scheduler.
  7. Define your SOURCE systems.
  8. Define your TARGET systems.
  9. HVR Load – this preps your tables for replication.
  10. HVR Refresh – This is the Instantiation/Initial Load part.
  11. HVR Replication – Start CDC (HVR Software doesn’t care if your system is live)
  12. HVR Compare – To prove you’re systems are synchronized. 10 min

4. DONE! Note: (bullets 3j and 3l are relative to the size of your data, the actual value will be supplied post QA benchmarking.)

In summary: Based on the above actual steps to implement HVR, replication can be up and running in under 25 minutes. And guess what? We don’t limit our functions, it’s truly a Total Cost of Ownership:

1. Replicate a certain amount of tables.

2. All HVR functions included.

Don’t believe it? Watch this video to see HVR explain in just about 10 minutes how to set up Oracle to SQL Server replication.

Request a trial license to test HVR in your environment!

About Mark

Mark Van de Wiel is the CTO for HVR. He has a strong background in data replication as well as real-time Business Intelligence and analytics.

© 2019 HVR

Try now Contact us