Understanding the SQAuto Engine
Welcome to SQAuto. This guide details our safety-first system architectures, legacy profiling tools, schema reconciliation workflows, and dialect translation pipelines.
What is SQAuto?
SQAuto is an embedded, migration-first data intelligence platform. It is engineered specifically to assist database developers, administrators, and architects in profiling, cleansing, repairing, and translating legacy SQL dumps before executing migrations to modern target systems.
SQL-File First Workflow
Unlike traditional ETL utilities that force online connections, SQAuto treats the SQL dump as the primary source of truth. We build safe, offline-first target exports so you have full code visibility before any database commits.
Staging Sandbox Isolation
Raw SQL dumps are treated as strict, read-only artifacts. All transformations, smart corrections, and diagnostics run inside isolated project sandboxes, guaranteeing that your production databases remain entirely safe.
Product Structure Hierarchy
The platform mirrors modern cloud setups, organizing resources cleanly to prevent data leakage and provide scope-level isolation:
Organization
The top-level tenant. Typically maps to a company division, a consulting firm, or a dedicated enterprise unit managing multiple clients.
Project
A specific migration initiative within an organization. For example, migrating "Legacy CRM Dump" to a modern PostgreSQL target.
Project Workspace & Sandbox
An active, project-scoped workspace powered by a SQL Dump Restore job. All diagnostic tools, graphs, mappings, and exports operate within this sandbox's boundaries.
Core Capabilities & Features
Schema Diagnostics
Fast extraction parses gigabyte-scale legacy files. Profiles table volumes, character encodings, row estimates, and detects primary/foreign key definitions.
Entity Reconciliation
Interactive mapping of source table properties to target fields. Compares ID ranges, analyzes constraint mismatches, and exposes data null risk patterns.
Smart Fix Repairs
Automatic discovery of orphan records, broken constraints, and duplicate rows. Apply deterministic fixes safely inside the staging sandbox first.
SQL Translation
Generate cleaned, production-ready DDL and DML scripts. Translate schemas accurately between PostgreSQL, MySQL, and SQLite dialects.
Staging Sandboxes
Perform dry-run executions in temporary environments. Dry-run queries and check targets without modifying target production.
Validation Gates
Enforce strict constraints (e.g. check for null percentages, duplicate keys, orphaned relations). Operators can manually override warnings.
The Migration User Flow
We recommend the following systematic workflow to guarantee safe database transitions:
1. Initialize Organization & Project
Setup your company organization and create a project specifying your source dialect, target dialect, and mapping goals.
2. Upload the Source SQL Dump
Upload your raw database backup. We isolate it in a read-only staging workspace and spin up a local diagnostic sandbox automatically.
3. Run Diagnostics & Inspect Data
Analyze row counts, primary key constraints, and check the integrity dashboards for orphaned tables or broken constraints.
4. Map Fields & Run Smart Repairs
Bind legacy columns to new target schemas. Apply deterministic fixes to repair missing relations, remove duplicates, or clean values.
5. Dry Run Validation & Dialect Export
Pass validation gates and export the final translated SQL migration file. You can also connect a live target DB to run a dry-run test push.
Safety & Staging Rules
Platform Safety Compliance Protocols
As a user-guided data intelligence tool, SQAuto enforces architectural restrictions to prevent accidental data corruption:
- Read-Only Source Dumps: SQL backup uploads are strict read-only files. They can never be altered by automatic scripts.
- Isolated Sandboxing: All data cleaning, schema manipulations, and relationship repairing happen on staging tables inside isolated sandboxes.
- Deterministic First: Algorithms prioritize strict database constraints and deterministic values over AI suggestions to guarantee schema precision.
- Validation Gates: Migration files are not generated if critical integrity tests fail (such as duplicate primary keys or high null rates) unless manually overridden and signed off by the operator.
Frequently Asked Questions
Is SQAuto a SaaS database?
No, SQAuto is not a host database. It is a data intelligence and migration staging suite. Its purpose is to analyze database backup dumps, profile anomalies, and export clean, ready-to-run SQL scripts for database engines (Postgres, MySQL, SQLite) hosted elsewhere.
Are my legacy SQL dumps safe?
Yes. All legacy SQL dumps are processed in project-scoped, local sandboxes. SQAuto prevents any cross-project data leaks, and your source database backup files are treated as strict, read-only files.
What SQL dialects are supported?
SQAuto parses SQL dumps and generates translated DDL/DML migration files matching three major relational database dialects: PostgreSQL, MySQL, and SQLite.