Databases

PostgreSQL, SQL Server and MySQL

Each engine is tested against real servers of every supported version, on every change, so a deployment does what its script says.

PostgreSQL

Tested on

131617

Deployments

Runs in one transaction. If any statement fails, nothing changes.

Tables, views and materialized views, functions and procedures, sequences, types, enums and domains, indexes, constraints, triggers, policies and extensions
Partitions and identity columns
Verified TLS with a root certificate file
Does not need access to the postgres database

SQL Server

Tested on

20192022

Deployments

Runs in one transaction. If any statement fails, nothing changes.

Tables, views, procedures, functions, synonyms, sequences, table types, partition functions and schemes, security policies, roles and permissions
History tables of system-versioned tables follow a renamed table
Accounts without VIEW DEFINITION compare what they can see, and Parallax says what to grant
Verified TLS with the CA installed in Windows or a server certificate file

MySQL

Tested on

8.08.4

Deployments

MySQL can't roll back schema changes, so Parallax rehearses the deployment on a scratch copy of the target's schema and checks the target's rows first.

Tables, views, procedures and functions, triggers, events, indexes and constraints
Accounts without SHOW_ROUTINE, TRIGGER, EVENT or SHOW VIEW compare what they can see
Rehearsal needs the right to create its scratch databases, or can be turned off
Verified TLS with a CA certificate file

Amazon RDS and other managed databases

Connect with the endpoint's name and, to verify the server, your provider's CA bundle. Accounts with fewer rights than a superuser work: what they can't see is left out on both sides.

Set up a managed database