Capabilities
This section describes the capabilities supported by Fivetran HVR on each location type.
Capture
This section lists the capabilities related to Capture.
| Capability | Support Status |
|---|---|
| Capture changes from location | Only supported on:
|
| Log-based capture (capture from DBMS logging system) | Only supported on:
|
| Capture from Archive log files only | Only supported on:
|
| Log-based capture of DDL statements using action AdaptDDL | Supported on all location types where Log-based capture (capture from DBMS logging system) is supported, except for:
|
| Log-based capture of tables without a primary key | Supported on all location types where Log-based capture (capture from DBMS logging system) is supported |
| Direct access to logs on a file system | Only supported on:
|
| Access to logs using SQL interface | Supported on all location types where Log-based capture (capture from DBMS logging system) is supported, except for:
|
| Log-based capture of tables with LOB column | Supported on all location types where Log-based capture (capture from DBMS logging system) is supported |
| Log-based capture from hidden rowid/RRN column (ColumnProperties with parameter CaptureFromRowId) | Only supported on:
|
| Rewind log-based capture to specific time (hvractivate option -i) | Supported on all location types where Log-based capture (capture from DBMS logging system) is supported, except for:
|
| Rewind log-based capture to specific time (hvractivate option -i) with Capture Method SQL | Only supported on:
|
| Rewind log-based capture to the beginning of currently active oldest transaction | Only supported on:
|
| Rewind log-based capture to the beginning of currently active oldest transaction for a specific list of tables | Only supported on:
|
| Online refresh using accurate LSN/SCN | Supported on all location types where Log-based capture (capture from DBMS logging system) is supported, except for:
|
| Online refresh skips capture log records early in scanner | Only supported on:
|
| Populates column hvr_cap_user for use in ColumnProperties {hvr_cap_user} substitutions | Only supported on:
|
| Log-based capture of truncate table statements | Only supported on:
|
| Multiple log-based capture jobs can capture from same database | Only supported on:
|
| Capture from tables with basic compression | Supported on all location types where Log-based capture (capture from DBMS logging system) is supported, except for:
|
| Capture from tables with advanced compression | Only supported on:
|
| Capture from tables with BLOB compression | Only supported on:
|
| Capture from tables with advanced index compression | Only supported on:
|
| Capture from tables with advanced row compression | Only supported on:
|
| Capture from tables with hybrid columnar compression | Only supported on:
|
| Log-based capture checkpointing using location property Capture_Checkpoint_Frequency | Only supported on:
|
| Read archives from an alternative directory (location property Archive_Log_Path on the capture location) | Only supported on:
|
| Trigger-based capture (location property Capture_Method=DB_TRIGGER on the capture location) | Only supported on:
|
| Location property Trigger_Quick_Toggle on the capture location | Only supported on: |
| Boundaries between transactions preserved by trigger-based capture | Only supported on:
|
| Trigger-based capture jobs can be woken by db-event when change happens | Only supported on:
|
Repository Database
This section lists the capabilities related to Repository Database.
| Capability | Support Status |
|---|---|
| Repository database | Only supported on:
|
Integrate
This section lists the capabilities related to Integrate.
| Capability | Support Status |
|---|---|
| Integrate changes into location | Only supported on:
|
| Burst integration (Integrate with parameter Method=BURST) | Supported on all location types where Integrate changes into location is supported, except for:
|
| Integrate with parameter BurstCommitFrequency | Supported on all location types where Integrate changes into location is supported, except for:
|
| Continuous integration (Integrate with parameter Method=CONTINUOUS) | Supported on all location types where Integrate changes into location is supported |
| Tables without a key and without TableProperties with NoDuplicateRows for continuous integration | Supported on all location types where Integrate changes into location is supported, except for:
|
| Continuous integrate with parameter OnErrorSaveFailed | Supported on all location types where Integrate changes into location is supported, except for:
|
| Disable/enable database triggers during integrate (with parameter NoTriggerFiring) | Only supported on:
|
| ColumnProperties with parameter SoftDelete | Supported on all location types where Integrate changes into location is supported |
| Bulk load requires a staging area (location property Staging_Directory) | Only supported on:
|
| Creation and update of HVR state tables | Supported on all location types where MinVersionRestrictions is supported, except for:
|
| Integrate with parameter DbProc | Only supported on:
|
Bi-directional Replication
This section lists the capabilities related to Bi-directional Replication.
| Capability | Support Status |
|---|---|
| Detection of changes made by HVR in a bidirectional channel to prevent loop-back | Only supported on:
|
| CollisionDetect with Log-based Capture (without parameter TimestampColumn) | Only supported on: |
| CollisionDetect with Trigger-based Capture (with location property Capture_Method=DB_TRIGGER on the capture location and CollisionDetect without parameter TimestampColumn) | Supported on all location types where Trigger-based capture (location property Capture_Method=DB_TRIGGER on the capture location) is supported |
| CollisionDetect with parameter TimestampColumn | Supported on all location types where Integrate changes into location is supported, except for:
|
Refresh and Compare
This section lists the capabilities related to Refresh and Compare.
| Capability | Support Status |
|---|---|
| hvrrefresh or hvrcompare from source location | Only supported on:
|
| Select more than 4 billion rows during hvrrefresh or hvrcompare | Supported on all location types where hvrrefresh or hvrcompare from source location is supported, except for:
|
| hvrrefresh into target location | Supported on all location types where MinVersionRestrictions is supported, except for: |
| Bulk load of multiple slices of same table can be done in parallel | Only supported on:
|
| Row-wise hvrrefresh into target location (option -g) | Supported on all location types where MinVersionRestrictions is supported, except for:
|
| Disable/enable foreign keys and secondary indices during hvrrefresh (option -F) | Only supported on: |
| Disable/enable constraints check during hvrrefresh | Only supported on:
|
| Disable/enable foreign keys from table to others during hvrrefresh (option -F) | Only supported on:
|
| For a table: disable/enable journaling, disable/enable unique/primary constraints, disable/enable volatile secondary indices, support main storage structure during hvrrefresh | Only supported on: |
| Disable/enable triggers during hvrrefresh (option -f) | Only supported on:
|
| Identity columns | Only supported on:
|
| Replicate database sequences (using action DbSequence) | Only supported on: |
| Suggestions in GUI for Slice Boundaries using DBMS statistics (hvrrefresh option -S) | Only supported on:
|
| Select data from each table from same consistent moment in time (hvrrefresh options -Mnow, -Mscn=val, -Mhvr_tx_seq=val, -Mtime) | Only supported on:
|
| Select data with 'snapshot' SQL isolation level (hvrrefresh option -Msnapshot) | Only supported on:
|
Other Capabilities
This section lists the capabilities related to Other Capabilities.