DataKitchen TestGen vs pgroll

DataKitchen TestGen profiles databases, generates data quality tests, and shows results and quality scores in dashboards. Its listed checks include 55 profiling characteristics, 32 hygiene detector tests, and 49 test types, including generated tests, business rules, and custom SQL. Monitors cover freshness, volume, schema, and custom metrics, using predictive models to flag changes such as late arrivals and schema drift. Supported databases include Snowflake, Databricks SQL, Azure Synapse Analytics, Azure SQL Database, SQL Server, OneLake, BigQuery, Redshift, Aurora PostgreSQL, Oracle 12c and later, SAP HANA, PostgreSQL, and Salesforce Data 360. It can also profile and test structured data in Iceberg, Parquet, Avro, ORC, CSV, and JSON through supported external-table options. TestGen runs in the customer’s infrastructure; DataKitchen says it does not host the application or receive customer data. It queries target databases with read-only access and stores results and metadata in its application database. The free Open Source plan is limited to one user, one connection, and one project. Enterprise costs $100 a month, billed per user and per database connection.

pgroll is an open-source command-line tool for PostgreSQL schema migrations that keeps old and new schema versions available while applications move between them. Its expand/contract workflow lets clients choose a version through PostgreSQL's search_path. The project describes migrations as zero-downtime and says it applies changes without locking the database; it can also backfill columns automatically when needed. For breaking changes, pgroll builds virtual schemas from views over physical tables and uses triggers to carry writes between old and new columns. Active migrations can be rolled back to the previous schema version. It supports PostgreSQL 14 and later, including RDS and Aurora, and is available for Linux, macOS, and Windows or self-hosting. It can convert SQL generated by ORMs, with examples for Alembic, Django, and Drizzle, though manual data migrations and SQL consolidation may be needed. On PostgreSQL 14, its versioned views do not respect row-level security policies, which can make it a poor choice for RLS users on that version. The project is licensed under Apache License 2.0.