This topic describes the versions of the Windows operating system and SQL Server that Delphix supports. For more information, please visit our support matrix documentation for SQL Server.
Supported Versions of Windows OS
Windows Server Version | Requirements for Staging/Target Hosts |
|---|---|
| Windows Server 2003 |
|
| Windows Server 2003 R2 |
|
| Windows Server 2008 |
|
| Windows Server 2008 R2 | |
| Windows Server 2012 | |
| Windows Server 2012 R2 | |
| Windows Server 2016 |
64-bit Windows only
Delphix supports only 64-bit versions of Windows on VDB Target Hosts and Staging Target Hosts. This restriction does not apply to Source Hosts.
Check OS Compatibility
The Windows Server OS versions on the Staging Target Hosts and VDB Target Hosts must be compatible.
Please refer to the compatibility matrices on this page: Windows Server OS and SQL Server DBMS Compatibility Matrices
SQL Server Failover Clusters
There are additional restrictions on supported Windows and SQL Server versions for SQL Server Failover Cluster target environments.
For details, see Adding a SQL Server Failover Cluster Target Environment.
Supported Versions of SQL Server
SQL Server Version | Delphix Version |
|---|---|
| SQL Server 2005 (9.0) | Delphix 3.x |
| SQL Server 2008 (10.0) | Delphix 3.x |
| SQL Server 2008 R2 (10.5) | Delphix 3.x |
| SQL Server 2012 (11.0) | Delphix 3.1.2 and beyond |
| SQL Server 2014 (12.0) | Delphix 4.1.3 and beyond |
| SQL Server 2016 (13.0) | Delphix 5.1.4 and beyond |
SQL Server Editions
For Staging Target Hosts, it is acceptable to use SQL Server Standard Edition even when the source databases are running SQL Server Enterprise Edition and contain EE features, such as partitioned tables. This is because EE-only features are not used during validated-sync operations.
However, for VDB target hosts, it is important to use the same edition of SQL Server software as the source database, so that all features available in the source are also available in the VDB.
Supported SQL Server Backup Software
- When linking a new dSource (creating a dSource), the Delphix Engine can use an existing full backup (preferred) or initiate a Delphix copy-only full backup to load the data from the dSource.
- When performing a SnapSync of an existing dSource, the Delphix Engine can use an existing full or differential backup.
- After creating the dSource, the Delphix Engine picks up any new backups that are taken on the dSource and applies them to the dSource. This includes:
- Transaction log backups for databases in Full or Bulk-Logged recovery models
- Differential and full backups for databases in Simple recovery model
Delphix currently supports the following software for dSource backups:
- SQL Server native backups
- Quest/NetVault LiteSpeed
If the dSource is backed up with LiteSpeed, the source and the Staging Target Host must also have LiteSpeed installed.
VDB target hosts do not need to have LiteSpeed installed.
- Delphix currently supports LiteSpeed v5.0.0.0 to v7.5. The version of LiteSpeed on the staging environment must be the same or higher than that on the source.
- On source SQL Server Instance, the dSource user must be granted execute privilege on extended stored procedure master.dbo.xp_sqllightspeed_version.
- Red Gate SQL Backup Pro
If the dSource is backed up with SQL Backup Pro, the source and the staging environments must have SQL Backup Pro installed on them.
Target environments do not need to have SQL Backup Pro.
- Delphix currently supports SQL Backup Pro v7.3 and onwards. The version of SQL Backup Pro on the staging environment must be the same as that on the source.
In versions 4.3.3.0 and newer, Delphix supports encrypted backups. If you are running an older version of the Delphix Engine (v 4.3.2.x - 3.0), encrypted backups are not supported.