Schema Comparison

Schema Comparison allows you to compare two database schemas and identify structural differences between them.

This feature helps you understand what has changed before updating a database, generating migration scripts, or synchronizing environments.

Instead of manually reviewing SQL files, Qubase automatically detects additions, modifications, and deletions across database objects.

Before you begin

Before comparing schemas, ensure that you have:

Connected to one or more databases
Selected two database schemas or versions
Read access to both schemas

[!NOTE] Schema Comparison analyzes database structures only. It does not modify either schema.

What can be compared?

Qubase compares many types of database objects, including:

Tables
Columns
Data types
Primary Keys
Foreign Keys
Constraints
Indexes
Views (when supported)

Comparison workflow


Select Source Schema
          │
          ▼
Select Target Schema
          │
          ▼
Analyze Structures
          │
          ▼
Detect Differences
          │
          ▼
Review Results

Perform a comparison

To compare two schemas:

Open Database Engineering.
Select Schema Comparison.
Choose the source schema.
Choose the target schema.
Start the comparison.
Review the detected differences.

Difference types

Qubase categorizes detected changes into several groups.

Change Type	Description
Added	New database objects
Removed	Deleted database objects
Modified	Existing objects that have changed
Renamed	Objects whose names have changed (when detected)

Example comparison


Source Schema
--------------
Users
Orders
Products

Target Schema
--------------
Users
Orders
Products
Categories

Comparison result:


+ Categories (Added)

Another example:


Users.email

VARCHAR(100)

↓

VARCHAR(255)

Comparison result:


Modified Column

Review changes

After the comparison completes, Qubase displays the detected differences.

You can review:

Added tables
Removed tables
Modified columns
Updated relationships
Changed constraints
Index modifications

This makes it easier to understand the impact of upcoming database updates.

Why use Schema Comparison?

Schema Comparison helps you:

Detect unexpected database changes
Validate deployment readiness
Review schema updates
Prepare migration scripts
Keep environments synchronized

Best practices

Compare development and production schemas before deployment.
Review all detected differences carefully.
Confirm unexpected changes with your team.
Keep schema versions under version control.

[!TIP] Compare schemas regularly to prevent configuration drift between development, staging, and production environments.