Keep your SQL Servers the same.
SQLParity compares the SQL Server instances that are supposed to match, shows you exactly what drifted, and lets you fix it with one reviewed click, so a failover never leaves you with orphaned users or missing jobs.
The server that fails over is the one nobody kept up to date.
A login is added on the primary and never on the DR server. A SQL Agent job is changed on one replica only. A password hash drifts, a linked server is missing, and the failover you tested last quarter fails in production with users who can no longer sign in.
SQLParity closes that gap. It compares the servers in each group on a schedule and shows you, side by side, what is different and which server has the version you want.
What SQLParity compares
The things that go out of step between SQL Server instances, checked for every group of servers.
Logins
Logins with their SIDs and password hashes, so users keep working after a failover, plus server roles and server permissions.
Agent jobs and operators
SQL Agent jobs and operators, so the same maintenance and alerts run wherever the databases are.
Linked servers
Linked servers that exist on one instance and are missing on another.
Database users and permissions
Database users, roles and permissions, including users orphaned from their login.
Hardware and configuration
CPU, memory, drives, instance facts and server configuration options, shown for comparison only. SQLParity never changes them unless you pick Copy for a configuration option yourself.
Groups of servers
Availability group replicas, DR pairs, migration copies or plain standalone servers. A server can be in several groups, and each group can have its own reference server and its own list of what to compare.
You stay in control
Report only, or fix on request. Nothing changes until you review the plan and click Go, and deleting anything needs you to type REMOVE.
Set it up once
Three steps, and then it watches your servers and tells you when they drift.
List your servers
Add each SQL Server instance with the sign-in SQLParity should use, then put the ones that should match into a group.
Let it compare
SQLParity checks each group on a schedule, or when you click Check now, and lists every difference with the servers side by side.
Decide and go
For each difference choose to copy it to the other servers, never report it, delete it, or do nothing for now, review the plan, and click Go.
Questions
Short answers to the things people ask first.
Does it send my server details or data to you?
No. SQLParity connects only to the SQL Server instances you list, from your own network. Server names, logins, jobs and settings are never sent to us. The only network traffic to us is the license check described in our privacy policy.
Does it need an availability group?
No. It works for availability group replicas, DR pairs, migration copies and ordinary standalone servers. When a server reports itself as an availability group primary, SQLParity uses it as the point of view automatically.
Will it change my servers without asking?
No. By default SQLParity only reports. Changes are made only when you review a plan and click Go. It never deletes anything unless you explicitly choose to remove an item, and removal asks you to type REMOVE first.
How does it run?
As a tray application on its own, or together with a Windows service that keeps checking while no one is signed in. The installer asks which you want, and you can switch later from the window.
What does one license cover?
Each license covers one installation, and one installation can compare any number of server groups. One purchase includes 2 licenses, for example one for the primary site and one for the DR site.
Can I try it first?
Yes, with a free 7-day trial you start from inside the app. An email address is required to start the trial; we also use it to send news and offers about SQLParity, and every message has an unsubscribe link.
How do I buy it?
See the Products & Services page for pricing and purchase options.
Find out before the failover does.
Let SQLParity show you what is different between your servers, and fix it on your terms.
View Products & Services