Capabilities for Azure SQL Managed Instance

This section lists the Capabilities of Fivetran HVR when using 'Azure SQL Managed Instance'. For more information about the pre-requisites, access privileges, and other configuration requirements, see Azure SQL Managed Instance Requirements.

Capture

HVR supports the following capabilities on Azure SQL Managed Instance:

• Capture changes from location.
• Log-based capture (capture from DBMS logging system).
• Log-based capture of tables without a primary key.
• Access to logs using SQL interface.
• Log-based capture of tables with LOB column.
• Online refresh using accurate LSN/SCN.
• Populates column hvr_cap_user for use in ColumnProperties {hvr_cap_user} substitutions.
• Multiple log-based capture jobs can capture from same database.
• Capture from tables with basic compression.
• Capture from tables with advanced compression.

HVR does not support the following capabilities on Azure SQL Managed Instance:

• Capture from Archive log files only.
• Direct access to logs on a file system.
• Log-based capture from hidden rowid/RRN column (ColumnProperties with parameter CaptureFromRowId).
• Rewind log-based capture to specific time (hvractivate option -i).
• Log-based capture of truncate table statements.
• Log-based capture checkpointing using location property Capture_Checkpoint_Frequency.
• Read archives from an alternative directory (location property Archive_Log_Path on the capture location).
• Trigger-based capture (using the location property Capture_Method=DB_TRIGGER at the capture location). This method has been deprecated since 6.2.0/0..

Repository Database

HVR supports Repository database on Azure SQL Managed Instance.

Integrate

HVR supports the following capabilities on Azure SQL Managed Instance:

• Integrate changes into location.
• Burst integration (Integrate with parameter Method=BURST).
• Integrate with parameter BurstCommitFrequency.
• Continuous integration (Integrate with parameter Method=CONTINUOUS).
• Tables without a key and without TableProperties with NoDuplicateRows for continuous integration.
• Continuous integrate with parameter OnErrorSaveFailed.
• ColumnProperties with parameter SoftDelete.
• Creation and update of HVR state tables.
• Integrate with parameter DbProc.

HVR does not support the following capabilities on Azure SQL Managed Instance:

• Disable/enable database triggers during integrate (with parameter NoTriggerFiring).

Bi-directional Replication

HVR supports the following capabilities on Azure SQL Managed Instance:

• Detection of changes made by HVR in a bidirectional channel to prevent loop-back.
• CollisionDetect with parameter TimestampColumn.

HVR does not support the following capabilities on Azure SQL Managed Instance:

• CollisionDetect with Log-based Capture (without parameter TimestampColumn).

Refresh and Compare

HVR supports the following capabilities on Azure SQL Managed Instance:

• hvrrefresh or hvrcompare from source location.
• hvrrefresh into target location.
• Row-wise hvrrefresh into target location (option -g).
• Disable/enable foreign keys from table to others during hvrrefresh (option -F).
• Disable/enable triggers during hvrrefresh (option -f).
• Identity columns.
• Select data with 'snapshot' SQL isolation level (hvrrefresh option -Msnapshot).

HVR does not support the following capabilities on Azure SQL Managed Instance:

• Bulk load of multiple slices of same table can be done in parallel.

Other Capabilities

HVR supports the following capabilities on Azure SQL Managed Instance:

• Call database procedure dbproc during replication jobs (AgentPlugin with parameter DbProc).
• DbObjectGeneration with parameter IncludeSQLFile.
• International table and column names where DBMS is not configured with UTF-8 encoding.
• Always treat DBMS table names and column names as case sensitive, even if not configured (equivalent to location property Case_Sensitive_Names always set to TRUE) .
• Always treat DBMS schema names case sensitive.

HVR does not support the following capabilities on Azure SQL Managed Instance:

• Use distribution key for parallelizing changes within a table (ColumnProperties with parameter DistributionKey).
• Distinguish and support capture from 'materialized views'.