We are constantly improving our comparison products and this page shares our vision for SQL Compare with you. The roadmap below gives an overview of what we are currently focusing on and our ideas for the future. We review our plans regularly and make changes based on new information, so keep an eye on this page to stay up to date.
We welcome your thoughts on these topics on our forums.
If you’d like to discuss any of the above ideas with our development team, please get in touch – we’d love to hear from you.
In SQL Compare 12.4 we have added a brand new way to examine the differences between two objects in your database. Up until now, SQL Compare has always relied on the SQL differences viewer to convey the differences between an object in the source database and its counterpart in the target database.
We have added an alternative way of viewing the differences between objects in a database. The new summary view provides a more concise view of the differences between two objects by getting rid of the SQL and showing only the semantic differences between objects in a much more structured way.
In addition to the new summary view, we have also made it easier to see why two tables are different when looking at the SQL difference viewer, so that it always displays the columns in an order that makes it clear exactly what the differences are.
We have also made changes to the colors used to show differences between the left and right hand sides, so that differences in the source database are shown in green and differences in the target database are shown in red.
By moving to this color scheme, commonly used in other diff viewer tools, we have increased visual contrast, making it easier to see at a glance where the differences between the source and target are. The change to the color scheme also makes it clearer that the changes to the source database, in green, will be added, or applied, to the target and those changes to the target database, in red, will be removed, or overwritten. This is in keeping with how most other diff viewer tools use red and green.
In SQL Compare 12.3 we have added a new option that will allow more control over what types of indexes are deployed. The "Ignore performance indexes" option will only deploy indexes created by unique constraints, primary keys, and foreign keys. This will allow the deployment of structural keys and indexes without impacting indexes that have been added to improve performance.
When using the SQL Source Control (v5.5.4 or later) data source you are now able to compare to a historical git revision.
In SQL Compare 12.2 we have added support for the comparison and deployment of temporal tables in SQL Server 2016.
This means you can include temporal tables when deploying changes and comparing differences to your SQL Server databases. You can see what’s changed in your current table, plus what will be added to the history table.
When you are ready to deploy, the script will include the expanded temporal table:
We’ve also added a handy warning that lets you know if you are deploying to an older version of SQL Server that doesn’t support temporal tables:
Support for temporal tables is available in SQL Compare 12.2 onwards. Make sure you’re on the latest version of SQL Compare by running Check for updates from the Help menu.
See full release notes.
SQL Compare 12.1 adds the ability to see when each object in the comparison results grid was last modified:
For tables, views, functions and stored procedures the comparison grid will show an extra column indicating when the object's schema last changed. The column can be sorted (by clicking on the column header) so that you can see at a glance which objects have changed recently.
You now have the ability to toggle the automatic mapping of similar columns. We have added this in response to feedback that the default behaviour (to always map similar columns) was undesirable in some situations. The new option can be found on the project Options tab under Auto-map similar columns:
By default SQL Compare automatically maps columns which have the same data types and similar names. This is to help detect renamed columns without the user having to map the columns manually.
This new option is selected by default so there is no change in behaviour for existing projects. To disable automatic mapping, un-check the option and click Save. When disabled, columns that SQL Compare would have mapped together automatically will now have to be mapped manually from the Table mapping tab.
Never miss another SQL Compare update with our new notification banner! When updates are available you will now be notified within the product. This will make it easier to know when updates have been released and what exciting new features have been added.
The new banner provides details about the features and fixes included and allows installation of the update. If you wish to update at a later date, or to skip an update these options are available from the Remind me drop down.
In response to a lot of feedback we have received since the release of SQL Compare 12 about how useful the My Projects section is, we have brought it back!
The new dialog allows you to view the details of the source and target for each project as well as when it was last modified. The list of projects can be filtered using the search box in the top-right corner.
You can access it from the File menu under My projects and, by checking the box at the bottom of the dialog, it can also be made to appear when the application starts up.
See full release notes.
We’ve completely overhauled the UI of SQL Compare to align it with our new common design guidelines. This has also allowed us to spend some time improving the underlying codebase, fixing over 200 UI related bugs in the process. This latest release sets us up to make small, quick improvements to the user experience.
When registering from a live database, scripts folder, or a snapshot, SQL Compare will now register both data sources at the same time, rather than waiting for your source to finish before starting on the target. This should speed up the comparison considerably.
You’ll notice SQL Compare asks you to sign in when you launch v12. That’s because we’ve introduced user account licensing, which will make it much easier for you to keep track of the tools you own and to move them between different machines.
SQL Compare 12 includes support for the following SQL Server 2016 features:
To access new features in SQL Compare as soon as they're ready, turn on frequent updates – they're typically released once a week. Learn more
Our roadmap contains details of what is coming next for SQL Compare. Check it out.