You can provision a Microsoft SQL Server Availability Group (AG) virtual database (VDB) in DCT by selecting a Windows Server Failover Cluster (WSFC) target environment with an Availability Group configured.

An AG VDB replicates across AG nodes and has different configuration and operation limits than a standalone SQL Server VDB.

Before you begin

Make sure that:

  • A WSFC environment with at least one Availability Group is registered in DCT.
  • The MSSQL engine is connected to DCT.
  • An appropriate MSSQL dSource exists.
  • You have permission to provision VDBs in DCT.

Provision an AG VDB

  1. Log in to DCT.
  2. Navigate to Data > Data Management > VDB and click Provision VDB. For more information, refer to Provisioning a SQL Server VDB.
  3. In the Target Environment step, select a WSFC target environment with an Availability Group configured.
  4. In the AG details panel, enter or verify the following values:
    FieldDescription
    AG NameName of the Availability Group on the WSFC cluster.
    Listener NameDNS name of the AG listener.
    Listener IPIP address of the AG listener.
  5. In the Target Config step, configure the AG provisioning settings.
    FieldDescription
    Backup BasedSelected by default. When selected, DCT provisions the AG VDB by using backup and restore from the primary replica. Clear Backup Based option to use Fast Provision. For more information, see the Provision a SQL Server AG virtual database.
    Backup Location(optional)Shared backup location used to provision the VDB on the AG cluster. This field appears when Backup Based is selected.
    Recovery ModelRead-only and set to FULL for AG VDBs.
    Change Data CaptureCan be configured during provisioning. After provisioning, this setting cannot be modified for AG VDBs.
  6. In the Hooks step, select a ConfigureClone hook if needed.
  7. Review the AG-specific values in the Summary step.
  8. Submit the workflow.
DCT does not pre-validate the AG topology before provisioning. If the selected environment is not a valid WSFC environment, the AG is unhealthy, or the target is also the source cluster, provisioning can fail as an engine-side provision job.

Limitations

  • Point-in-time provision and point-in-time refresh are not supported for non-backup-based AG VDBs.
  • Snapshot and Retention policies are not available. Only ConfigureClone hooks are available.
  • Recovery Model is always FULL.
Last updated
Oct 9, 2026