Comments
Sort by recent activity
Hi, thanks for reaching out. Currently, SQL Data Compare does not fully support the JSON data type, which can lead to the error you're seeing. A common workaround is to cast the JSON column to NVARCHAR in a view and compare the views instead of the base tables. While there's no official timeline for native JSON support, we recommend keeping an eye on Redgate’s release notes or submitting feedback directly to influence future updates. Let me know if you’d like help setting up the workaround. / comments
Hi, thanks for reaching out. Currently, SQL Data Compare does not fully support the JSON data type, which can lead to the error you're seeing. A common workaround is to cast the JSON column to NVAR...
Hi! Redgate SQL Compare doesn’t natively compare row counts or include them in its HTML reports (checkout). It focuses on schema differences, not data. However, Redgate SQL Data Compare can compare data and could be scripted via command line to highlight row differences. For just row counts, you might consider a custom script or PowerShell command to query both servers and compare row counts per table—then output the results alongside your SQL Compare report. Let me know if you'd like help setting that up! / comments
Hi! Redgate SQL Compare doesn’t natively compare row counts or include them in its HTML reports (checkout). It focuses on schema differences, not data. However, Redgate SQL Data Compare can compare...