SQL Data Compare 16.1 release notes
Published 23 July 2026
What's new in SQL Compare 16.1
Warnings for risky WHERE clauses
If you use a WHERE clause to filter the rows included in a comparison, SQL Data Compare now checks it before you run the comparison and warns you if it looks unsafe. For example, it flags functions we don't recognize or a stray ; that could interfere with the generated script. Filters using standard T-SQL syntax will validate without any extra prompts.
16.1.6.29333 - 18 August 2026
FREQUENT UPDATES RELEASE
Bug fix
- ZD-361357: The number of progress events reported when performing column mappings has been capped. This prevents the UI being overwhelmed with events and hanging the application.
- ZD-362488: Fixed the deployment script header omitting the source control revision number when comparing SQL Source Control “Data Source” revisions
16.1.5.29295 - 12 August 2026
FREQUENT UPDATES RELEASE
Bug fix
- ZD-360534: Fixed “FieldMapping not valid for MatchingMappings” error when comparing databases containing AS EDGE or AS NODE graph tables with no primary key
16.1.4.29264 - 06 August 2026
FREQUENT UPDATES RELEASE
Compatibility with SQL Compare 16.1.4.29264
16.1.3.29242 - 31 July 2026
FREQUENT UPDATES RELEASE
Bug fix
- ZD-360661: WHERE clause validation no longer warns about valid T-SQL such as NOT LIKE, EXISTS and subqueries
16.1.2.29188 - 23 July 2026
FREQUENT UPDATES RELEASE
Compatibility with SQL Compare 16.1.2.29188
16.1.1.29148 - 14 July 2026
FREQUENT UPDATES RELEASE
Compatibility with SQL Compare 16.1.1.29148
16.1.0.29116 - 06 July 2026
New feature
- SQL Data Compare command line now stops if your project’s WHERE clauses might have unintended side effects. Please pass /AllowDangerousWhereClauses as an option to compare anyway
This documentation contains proprietary information and is protected by copyright law.
Copyright © 2026 Red Gate Software Limited. All rights reserved
