Azure SQL Database as Source

Since v6.1.0/3

Since 6.1.5/4, support for Capture from the Azure SQL Database has been deprecated. However, you can still configure it using the CLI or REST API, but not via the HVR UI.

Support for Capture from the Azure SQL Database will be removed entirely in one of the future HVR 6 releases.

Capture

Fivetran HVR allows you to Capture changes from Azure SQL Database. HVR uses SQL Server ODBC driver to capture changes from an Azure SQL Database location. This section describes the configuration requirements for capturing changes from Azure SQL Database location.

Table Types

HVR supports capture from the following table types in Azure SQL Database:

• clustered (row/page compressed and uncompressed)
• heap (row/page compressed and uncompressed)

HVR does not support capture from memory optimized tables and temporal tables.

Capture Methods

HVR supports only the following method for capturing (Capture) changes from Azure SQL Database:

Trigger-based Capture

In this capture method (Capture_Method=DB_TRIGGER), HVR capture changes through DBMS triggers generated by HVR.

Grants for Trigger-based Capture

This section lists the grants required for capturing changes from Azure SQL Database using database triggers.

• The HVR database User must be a database owner (db_owner role).

Compare and Refresh from Azure SQL Database

HVR allows you to perform only Compare and Refresh from Azure SQL Database (without using Capture). This section describes the configuration requirements for performing only Compare and Refresh from Azure SQL Database.

Grants for Compare and Refresh from Azure SQL Database

This section lists the grants required for performing only Compare and Refresh from Azure SQL Database. Based on your requirement, the HVR database User must be granted either of the permissions listed below.

• DbOwner
  The HVR database User must be granted db_owner role for the source database.

• Minimal
  In this permission model, the HVR database User does not need to be a database owner.

If the HVR database User needs to select from tables in another schema (for example if action TableProperties is defined with parameter Schema), then the following select privileges should be granted.

grant select to username; -- Let HVR read all tables

grant select on schema::dbo to username; -- Let HVR only read DBO tables