Database Vault currently supports Microsoft SQL Server and Oracle's MySQL. The following versions of each server have been validated to work with Database Vault: SQL Server 2014, SQL Server 2012, SQL Server 2008 R2, MySQL 5.6.x, and MySQL 5.7.x. Other versions may work, but have not been validated. Support is not provided for versions of servers not shown above.

Using a validated database version ensures that Database Vault can reliably apply its security controls without encountering engine-level incompatibilities. The product integrates at a low level with the database to enforce encryption, privileged access restrictions, and related protections. Running an untested release risks incomplete functionality, installation errors, or unpredictable behavior under load. Administrators should verify their environment against this list early in the planning phase to avoid downstream issues during deployment or production use.

#Supported Microsoft SQL Server Versions

The validated SQL Server releases received extensive testing across common configurations, including different editions and service packs. These versions were chosen because they represent stable platforms widely used in enterprise environments at the time of validation. Sticking to them allows Database Vault to leverage the expected behavior of the database engine for its core operations.

  • SQL Server 2014
  • SQL Server 2012
  • SQL Server 2008 R2

Each of these releases has been confirmed to allow full operation of Database Vault features. It remains the responsibility of the operator to keep the chosen SQL Server instance updated with vendor-recommended patches for security and stability, while staying within the major version listed.

#Supported MySQL Versions

Oracle's MySQL releases listed below were tested for compatibility with Database Vault on both Windows and Linux hosts where applicable. The validation focused on standard MySQL behavior for storage engines, user management, and query processing that Database Vault depends upon.

  • MySQL 5.6.x
  • MySQL 5.7.x

These minor version branches provide the API and feature stability required. Newer major releases such as MySQL 8.0 introduce significant changes that have not been validated and are therefore outside the supported scope.

#Verifying Your Current Database Version

Before installing or configuring Database Vault, always confirm the exact version of your database server. This quick check prevents surprises and confirms you are operating within the supported matrix. The queries below return the version string that can be compared directly against the validated list.

#SQL Server Version Query

tsql 
SELECT
    @@VERSION AS SQLServerVersion,
    SERVERPROPERTY('ProductVersion') AS ProductVersion,
    SERVERPROPERTY('Edition') AS Edition;

Run the statement above in SQL Server Management Studio, Azure Data Studio, or any query tool connected with sufficient privileges. The output provides the full version banner, product level, and edition, allowing precise identification of whether your instance falls within the supported set.

#MySQL Version Query

sql 
SELECT VERSION() AS MySQLVersion;
SHOW VARIABLES LIKE 'version%';

Execute these statements through the mysql client, MySQL Workbench, or your preferred query interface. The VERSION() function returns the server version string; the additional SHOW VARIABLES command supplies related build details that can help during troubleshooting.

#Support Policy and Common Pitfalls

Only the versions explicitly listed above are validated and supported. While it is possible that an unlisted release, such as a newer SQL Server or MySQL 8.x, might allow basic operation, these configurations have not undergone testing. Consequently, no technical support is available for problems encountered on unsupported versions. Common pitfalls include assuming forward compatibility with newer database releases, overlooking required service packs on older SQL Server instances, or deploying on MySQL variants that deviate from the official Oracle builds. Each of these can lead to silent failures or reduced security effectiveness.

In production environments, the cost of an unsupported configuration can be significant if issues arise that cannot be reproduced on validated platforms. Always perform functional and security testing of Database Vault on a staging system that exactly mirrors your intended production database version.

Align your infrastructure with the validated versions of SQL Server or MySQL to maintain full compatibility and receive support when needed. This approach ensures Database Vault delivers consistent data protection without introducing untested variables into your environment.