This could open up a whole new opportunity of sales for RedGate. QA and Regression Testing have no good means of seeing what data is being changed by programming changes currently. It would be excellent to have! Thanks.

An HTML report similar to the one provided with the SQL Schema Compare utility would be an excellent tool for doing QA Testing and Regression Testing. The QA Analyst could send the HTML report link to programmers to fix erroneous data. (The databases being compared would be the Pre-Test versus the Post-Test data.)

Yes. A feature to export the report from SQL Data Compare as an HTML or an EXCEL would be more productive . When we have thousands of records with differences, a CSV file is not useful. It would be useful if we can generate a report with the differences showing in different colors. You have the feature on the UI where it's showing the differences but need this in the report also.

It would also be great to be able to provided the vendor of the actual live application with a formatted report. Showing what is different on each row.

I support the Data Warehouse of an Urgent Care Application. The client who are non technical users would like a formatted report of the differences that we have detected during external data refreshes for example.

why did you remove this?
unreadable csv file output - no good.
the HTML report was one of the best features
enough to make me stop using the latest version and go back to an earlier version of the tool
:-(

Having a non-tech report highlighting the compare differences would be great.

HTML reports are greatly needed for using compare reports as deliverables

I vote for this and strongly encourage to get this incorporated in new release of the product. This would make the product more valuable as well.

Please approve this

I would like to vote for this as well agian would increase its usefulness to us

Please add this - would greatly benefit how we use the tool.

This would be a huge plus for our organization. Please add this to the next version.

The DBA team gets a request from a developer to do a data compare - we'd like to give them an easily understandable report. We also get requests from the deployment team - can we push configuration differences from a beta db to a prod db? But they want a report first so they can say, push this table's differences but not this other table's differences.

This request has been submitted multiple times now.

This is definitely something we're considering, especially as these tools are used more and more for build processes such as continuous integration. Out of interest, could you describe briefly how your build process works?

I would like to see SQL Data Compare get the /report switch like SQL Compare does. With SQL Compare I usually generate an interactive report to store along the generated script in our build process. This allows to review changes packaged into a given build. Having the same kind of reporting capability from SQL Data Compare would allow us to get the full picture of a given build's database changes (for static data, precisely).