Capabilities for Azure SQL Database

From HVR
Jump to: navigation, search

This section describes the capabilities supported by HVR on Azure SQL Database. For more information about the requirements, access privileges, and other features of HVR when using Aurora MySQL for replication, see Requirements for Azure SQL Database.

Capture

HVR supports the following capabilities on Azure SQL Database:

  • Capture changes from location
  • Trigger-based capture (action Capture /TriggerBased)


HVR does not support the following capabilities on Azure SQL Database:

  • Log-based capture (capture from DBMS logging system)


HVR Hub

HVR supports Hub database on Azure SQL Database


Integrate

HVR supports the following capabilities on Azure SQL Database:


HVR does not support the following capabilities on Azure SQL Database:

  • Disable/enable database triggers during integrate (/NoTriggerFiring)


Bi-directional Replication

HVR supports the following capabilities on Azure SQL Database:


Refresh and Compare

HVR supports the following capabilities on Azure SQL Database:

  • Refresh or Compare from source location
  • Refresh into target location
  • Row-wise refresh into target location (option -g)
  • Disable/enable foreign keys from table to others during refresh (option -F)
  • Disable/enable triggers during refresh (option -f)
  • Select data from each table from same consistent moment in time using a single transaction (and session) with 'serializable' SQL isolation level (refresh option -Mserializable)
  • Select data from each table from same consistent moment in time using a single transaction (and session) with 'snapshot' SQL isolation level (refresh option -Msnapshot)


Other Capabilities

HVR supports the following capabilities on Azure SQL Database:

  • Use distribution key for parallelizing changes within a table (ColumnProperties /DistributionKey)
  • Call database procedure dbproc during replication jobs (action AgentPlugin /DbProc)
  • DbObjectGeneration with /IncludeSQLFile
  • International table and column names where DBMS is not configured with UTF-8 encoding