Users of of the HVR technology have to manage their own HVR installation.
When you start using HVR 6, or you migrate from version 5 to 6, you may wonder: how do I size my HVR hub server. The HVR documentation provides high-level guidelines. In this p...
This post only applies to the use of the Fivetran HVR technology.
HVR provides two integration method:
Continuous: with the continuous method changes are processed row-by-row in the order the changes were committed on the source.Burst: with the use o...
Most Fivetran customers consolidate data from multiple sources into a destination platform. The top three most popular destinations are Snowflake, Google BigQuery and Databricks, but other platforms are commonly used also. Most integrations target an...
Most relational online transaction processing (OLTP) databases use a transaction log. The transaction log is the ledger for changes to the database, and the foundation for database recovery. Database changes are only committed when they have successf...
Snowflake is one of the most popular destinations for Fivetran, also with the use of the HVR Technology. When Fivetran syncs data into Snowflake we stage data using files.
This post covers considerations between using external and internal staging.
W...
Hi Terry,If you have activity only a few times during the day with no activity whatsoever in between then the use of action Scheduling IntegrateStartAfterCapture would be good to use (in conjunction with a quick shutdown on your Snowflake warehouse)....
Hi Terry,Unfortunately it is not as simply as you suggest option b would be. HVR performs a number of steps in a single transaction which implies it must run as a single session. We rely on Snowflake transactional consistency to ensure in case of pro...
Hi Terry,On the source the HVA generally does not generate files. The HVA captures changes as they happen in the transaction log - based on the channel definition - in memory and propagates as soon as the commit happens. There are two scenarios that ...
