Run SQLCompare core comparisons across tables, SQL queries, and files to produce a diff_id. Use when the user wants to compare two datasets, choose index keys, set connectors, or run dataset configs via sqlcompare run subcommands or sqlcompare query.
Run the primary SQLCompare commands that create comparison artifacts and return a diff_id for later analysis. Focus on selecting inputs, defining index keys, and choosing the right connector.
Use these patterns to pick the right entry point.
sqlcompare run table analytics.fact_sales analytics.fact_sales_new idsqlcompare run query --previous "SELECT ..." --current "SELECT ..." --index id -c snowflake_prod
sqlcompare run query --previous queries/previous.sql --current queries/current.sql --index id -c snowflake_prodsqlcompare run file path/to/previous.csv path/to/current.xlsx idsqlcompare run dataset path/to/dataset.yamlsqlcompare run stats analytics.users analytics.users_new -c snowflake_prodsqlcompare query "SELECT COUNT(*) FROM analytics.users" -c snowflake_prodsqlcompare run table analytics.users analytics.users_new user_id,tenant_id-c <name> to select a named connection for a run.SQLCOMPARE_CONN_DEFAULT for the default connector.SQLCOMPARE_CONN_<NAME> for named connectors.~/.sqlcompare/connections.yml for YAML-based connection configs.sqlcompare-output-analysis for inspection, exports, and queries.SQLCOMPARE_COMPARISON_SCHEMA (default sqlcompare).CREATE SCHEMA and CREATE TABLE privileges.