This documentation is for an older version of HVR.
Capabilities for SQL Server
This section lists the Capabilities of HVR when using 'SQL Server'. For more information about the pre-requisites, access privileges, and other configuration requirements, see Requirements for SQL Server.
Capture
HVR supports the following capabilities on SQL Server:
- Capture changes from location (SQL Server from 2000 (with SP1+) to 2019).
- Log-based capture (capture from DBMS logging system) (SQL Server from 2005 to 2019).
- Capture from Archive log files only (SQL Server from 2005 to 2019, except on Amazon RDS for SQL Server, Google Cloud SQL for SQL Server, and Microsoft Azure SQL Database).
- Log-based capture of tables without a primary key (SQL Server from 2008 to 2019).
- Direct access to logs on a file system (SQL Server from 2005 to 2019, except on Amazon RDS for SQL Server, Google Cloud SQL for SQL Server, and Microsoft Azure SQL Database).
- Access to logs using SQL interface (SQL Server from 2005 to 2019).
- Log-based capture with /LogReadMethod parameter (SQL Server from 2005 to 2019).
- Log-based capture of tables with LOB column (SQL Server from 2005 to 2019).
- Rewind log-based capture to specific time (Hvrinit option -i) (SQL Server from 2005 to 2019).
- Rewind log-based capture to the beginning of currently active oldest transaction (SQL Server from 2005 to 2019).
- Rewind log-based capture to the beginning of currently active oldest transaction for a specific list of tables (SQL Server from 2005 to 2019).
- Online refresh using accurate LSN/SCN (SQL Server from 2005 to 2019).
- Online refresh skips capture log records early in scanner (SQL Server from 2005 to 2019).
- Populates column hvr_cap_user for use in ColumnProperties {hvr_cap_user} substitutions (SQL Server from 2005 to 2019).
- Multiple log-based capture jobs can capture from same database (SQL Server from 2005 to 2019, only FN mechanism, not SP).
- Capture from tables with (data_compression=row) (SQL Server from 2008 to 2019).
- Capture from tables with (data_compression=page) (SQL Server from 2008 to 2019).
- Hvrlogrelease to preserve journal/archives (SQL Server from 2005 to 2019).
- Read archives from an alternative directory (Capture /ArchiveLogPath) (SQL Server from 2005 to 2019).
- Trigger-based capture (action Capture /TriggerBased) (SQL Server from 2000 (with SP1+) to 2019).
- Boundaries between transactions preserved by trigger-based capture (SQL Server from 2000 (with SP1+) to 2019).
- Trigger-based capture jobs can be woken by db-event when change happens (SQL Server from 2008 to 2019).
HVR does not support the following capabilities on SQL Server:
- Log-based capture from hidden rowid/RRN column (ColumnProperties /CaptureFromRowId).
- Log-based capture of truncate table statements.
- Log-based capture checkpointing (action Capture /CheckpointingFrequency).
Hub Database
HVR supports Hub database on SQL Server.
Integrate
HVR supports the following capabilities on SQL Server:
- Integrate changes into location (SQL Server from 2000 (with SP1+) to 2019).
- Integrate with /Burst (SQL Server from 2000 (with SP1+) to 2019).
- Integrate with /BurstCommitFrequency (SQL Server from 2000 (with SP1+) to 2019).
- Continuous integration (Integrate without /Burst) (SQL Server from 2000 (with SP1+) to 2019).
- Action TableProperties with /DuplicateRows for continuous integration (SQL Server from 2000 (with SP1+) to 2019).
- Continuous Integrate with /OnErrorSaveFailed (without /Burst) (SQL Server from 2000 (with SP1+) to 2019).
- Disable/enable database triggers during Integrate (/NoTriggerFiring) (SQL Server from 2000 (with SP1+) to 2019).
- Action Transform /SoftDelete (SQL Server from 2000 (with SP1+) to 2019).
- Creation and update of HVR state tables (SQL Server from 1998 to 2019).
- Integrate with /DbProc (SQL Server from 2000 (with SP1+) to 2019).
Bi-directional Replication
HVR supports the following capabilities on SQL Server:
- Detection of changes made by HVR in a bidirectional channel to prevent loop-back (SQL Server from 2000 (with SP1+) to 2019).
- CollisionDetect with Trigger-based Capture (with Capture /TriggerBased and without CollisionDetect /TimestampColumn) (SQL Server from 2000 (with SP1+) to 2019).
- CollisionDetect with /TimestampColumn (SQL Server from 2000 (with SP1+) to 2019).
HVR does not support the following capabilities on SQL Server:
- CollisionDetect with Log-based Capture (without /TimestampColumn).
Refresh and Compare
HVR supports the following capabilities on SQL Server:
- Hvrrefresh or Hvrcompare from source location (SQL Server from 1998 to 2019).
- Hvrrefresh into target location (SQL Server from 1998 to 2019).
- Row-wise Hvrrefresh into target location (option -g) (SQL Server from 1998 to 2019).
- Disable/enable foreign keys from table to others during Hvrrefresh (option -F) (SQL Server from 1998 to 2019).
- Disable/enable triggers during Hvrrefresh (option -f) (SQL Server from 1998 to 2019).
- Identity columns (SQL Server from 2000 (with SP1+) to 2019).
- Select data from each table from same consistent moment in time using a single transaction (and session) with 'serializable' SQL isolation level (Hvrrefresh option -Mserializable) (SQL Server from 1998 to 2019).
- Select data from each table from same consistent moment in time using a single transaction (and session) with 'snapshot' SQL isolation level (Hvrrefresh option -Msnapshot) (SQL Server from 1998 to 2019).
Other Capabilities
HVR supports the following capabilities on SQL Server:
- Use distribution key for parallelizing changes within a table (ColumnProperties /DistributionKey) (SQL Server from 1998 to 2019).
- Call database procedure dbproc during replication jobs (action AgentPlugin /DbProc) (SQL Server from 2000 (with SP1+) to 2019).
- DbObjectGeneration with /IncludeSQLFile (SQL Server from 2000 (with SP1+) to 2019).
- International table and column names where DBMS is not configured with UTF-8 encoding (SQL Server from 1998 to 2019).
- Treat DBMS table names and columns as case sensitive if configured (action LocationProperties /CaseSensitiveNames defined) (SQL Server from 1998 to 2019, since HVR 5.6.5/1).
- Always treat DBMS table names and column names as case sensitive, even if not configured (action LocationProperties /CaseSensitiveNames not defined) (SQL Server from 1998 to 2019).
- Always treat DBMS schema names case sensitive (SQL Server from 1998 to 2019).
HVR does not support the following capabilities on SQL Server:
- Distinguish and support capture from 'materialized views'.