dbHydrate
Try dbHydrate
SQLServer-dbHydrateMicrosoft SQL Server 2017–2022 · Azure SQL

Microsoft SQL Server changes.
Reviewed before they run.

Compare schemas. Rehearse every change inside a transaction that is rolled back, then apply it in one transaction.

Try Microsoft SQL ServerSee it in action
PostgreSQL example: schema objects, generated SQL, impact summary and target confirmation in the dark dbHydrate workspace
dbHydrate workspace · select to enlargeDesign preview · PostgreSQL example data

Select differences, inspect SQL, and rehearse a change before applying it.

  1. 01Select

    Choose the objects to review.

  2. 02Inspect

    Read the generated SQL side by side.

  3. 03Validate

    Check warnings and rehearse the plan.

THE CHANGE, IN CONTEXT

See exactly what will change.

Keep the source, target and decisions together. Select the differences you want to include before applying them.

Target · currentUAT
CREATE TABLE dbo.Customers (
  Id bigint PRIMARY KEY,
  first_name varchar(80),
  email varchar(255)
);
Source · desiredDEV
CREATE TABLE dbo.Customers (
  Id bigint PRIMARY KEY,
  first_name varchar(80),
  email varchar(255),
  phone varchar(32)
);

+ One reviewed column

  • Selected objectsFocus on the tables, indexes and views that matter.
  • Generated SQLInspect current and desired definitions.
  • Reviewed warningsCheck impact, dependencies and the target.

Illustrative definitions. Review the actual plan for your database.

SQL Server rolled-back dry runs

Rehearse the supported plan in a target transaction, then roll it back. Review transaction-incompatible statements and locks separately.

  1. 1
    CompareIdentify differences.
  2. 2
    Dry runRehearse the plan.
  3. 3
    ConfirmReview and approve.
  4. 4
    ApplyExecute on the target.

Manage users & access

Create users, update accounts, and add or remove database access. Review engine-specific roles and permissions before applying.

View the access workspace
Engine details & considerations
BUILT FOR SQL SERVER

See it work before it runs.

dbhydrate reads the live Microsoft SQL Server catalog, orders every change by its dependencies, and rehearses the whole plan before you decide.

Rolled-back dry runs

The full plan runs on the target inside a transaction that is rolled back. You see which statement would fail before anything changes. Then it is applied in one transaction.

BEGIN TRANSACTION;
ALTER TABLE dbo.Orders ADD Status nvarchar(32) NOT NULL CONSTRAINT DF_Orders_Status DEFAULT N'pending';
ROLLBACK; -- Dry run: nothing is kept

Changes in the right order

Default constraints, schema-bound views, indexes and foreign keys are dropped and recreated in dependency order. dbhydrate never uses CASCADE.

-- Staged by dependency
1. drop schema-bound view: dbo.vOrderTotals
2. alter column: dbo.Orders.Amount
3. recreate view: dbo.vOrderTotals

Your sign-in, kept local

Connect with a SQL login, Microsoft Entra ID (password or service principal) or Windows sign-in. Secrets are encrypted on your computer and never sent anywhere else.

encrypt: strict · mandatory · optional
sign-in: SQL login · Entra ID · Windows

Safe sources, clear notices

Sources are read inside a transaction that is always rolled back. If the source login can write, dbhydrate tells you on screen, and blocks it on high-protection connections.

Notice: this login can write to the source.
Use a read-only login for full protection.
SQL SERVER DETAILS

Frequently asked questions.

Which Microsoft SQL Server versions does dbhydrate support?

dbhydrate supports Microsoft SQL Server 2017, 2019 and 2022, on premises, in virtual machines or in Docker, as well as Azure SQL Database and Azure SQL Managed Instance.

How can I sign in to Microsoft SQL Server?

With a SQL login (user name and password), with Microsoft Entra ID (password or service principal), or with Windows sign-in using a domain user and password. Passwords and secrets are stored encrypted on your computer and never leave it.

How does dbhydrate rehearse a change on Microsoft SQL Server?

Microsoft SQL Server can roll back most schema changes. dbhydrate runs the whole plan on the target inside a transaction and then rolls it back, so you see exactly which statement would fail without changing anything. No shadow database is needed. The few statements that cannot run in a transaction are labelled in the plan before you apply.

How does dbhydrate keep a Microsoft SQL Server source read-only?

Microsoft SQL Server cannot lock a session to read-only. dbhydrate reads a source database inside a transaction that is always rolled back, checks whether the login can write and warns you if it can, and blocks unsafe filter text. The app tells you on screen whenever one of these safeguards applies. For full protection, use a login that can only read.

Does a Microsoft SQL Server license include PostgreSQL or MySQL?

No. SQLServer-dbHydrate is a separate product. Each license works in the product it was bought for. See the current device allowance per purchased seat on the pricing page.

Bring clarity to your next
Microsoft SQL Server change.

14-day trial · Starts when you register in the desktop app. Each purchased seat allows 1 device(s).

Try Microsoft SQL ServerView pricing