Capabilities for BigQuery

Last updated on Sep 17, 2021

Contents

This section lists the Capabilities of HVR when using 'BigQuery'. For more information about the pre-requisites, access privileges, and other configuration requirements, see Requirements for BigQuery.

Capture

HVR does not support Capture changes from location on BigQuery.

Hub Database

HVR does not support Hub database on BigQuery.

Integrate

HVR supports the following capabilities on BigQuery:

  • Integrate changes into location (BigQuery version 2).
  • Burst integration (Integrate with /Burst) (BigQuery version 2).
  • Integrate with /BurstCommitFrequency (BigQuery version 2).
  • Continuous integration (Integrate without /Burst) (BigQuery version 2).
  • Action Transform /SoftDelete (BigQuery version 2).
  • Bulk load requires a staging area (LocationProperties /StagingDirectoryHvr) (BigQuery version 2).
  • Creation and update of HVR state tables (BigQuery version 2).

HVR does not support the following capabilities on BigQuery:

  • Action TableProperties with /DuplicateRows for continuous integration.
  • Continuous integration with /OnErrorSaveFailed.
  • Disable/enable database triggers during Integrate (/NoTriggerFiring).
  • Integrate with /DbProc.

Bi-directional Replication

HVR does not support Bi-directional Replication on BigQuery.

Refresh and Compare

HVR supports the following capabilities on BigQuery:

Other Capabilities

HVR supports the following capabilities on BigQuery:

  • International table and column names where DBMS is not configured with UTF-8 encoding (BigQuery version 2).
  • Treat DBMS table names and columns case sensitive (action LocationProperties /CaseSensitiveNames) (BigQuery version 2).
  • Always treat DBMS table names and column names case sensitive (BigQuery version 2).
  • Always treat DBMS schema names case sensitive (BigQuery version 2).

HVR does not support the following capabilities on BigQuery:

  • Use distribution key for parallelizing changes within a table (ColumnProperties /DistributionKey).
  • Lossless binary float datatypes. No data loss when transporting float values (because base 2 fractions are never converted to base 10).