Contents 

AdeptSQL Diff Reference
AdeptSQl Diff versions, history and milestones
Supported versions of MS SQL Server
Getting started
Connecting to databases
Scanning available servers
Saving and opening comparisons
Running from command line
Diff in portable mode
Working with the schema
Viewing schema differences
Ignored Differences
Comparing objects side-by-side
Dragging and dropping schema items
Using schema filters
Generating comparison reports
Customizing the reports
Executing the SQL
SQL errors and warnings
Transaction support
Keyboard shortcuts
Editing commands and keyboard shortcuts
Using keyboard templates
Choosing debugger's key mapping
Comparing table data
DataDiff overview
DataDiff configuration dialog - table-level
DataDiff configuration dialog - columns
Special situations comparing data
Exporting data to Excel
DataDiff Reports
Column configuration file
Configuring AdeptSQL Diff
Options dialog
Schema Scan
Selective Loading
Comparison
Name Comparison
Code Comparison
User-defined types
Indexes and Statistics
Permissions and XProps
Synonyms
Other details to ignore
Scripting
General logic
Side-by-side scripting
Formatting
Identifiers
Schema Level
Tables
Constraints
Default Values
Procedures, Views, etc
Visuals
Text Fonts
Schema Tree
Summary collections
Side-by-Side View
Suppressed dialogs
Data comparison options
General
Scripting
Column Config File
Using COM Automation interface
Automating schema comparison
Automating data comparison
Licensing and contact info
Registration of AdeptSQL Diff
License conditions
Contact information

AdeptSQL Diff Online Help

Prev Page Next Page

DataDiff Reports

Top  Previous  Next

datadiff_report

 

Starting from version 1.90, the DataDiff contains a reporting feature.  The snapshot above shows how the reporting is initiated.  The intermediate dialog allows to choose a report template (only one of which is currently implemented) and set some basic parameters: whether the entire data comparison should be scripted, or just the selection, or only the column lists and statistics.

Note 1: The current report implementation simply ignores any columns that go beyond the page width.  If your tables are "wide" (and most real-life tables contain more columns than can be fitted across an A4 page) and you need to print the data comparison report, consider including into the comparison only those columns that you need to see in the report, marking all others as Ignored.  Alternatively, you can use the XML export feature which correctly works with any number of columns.

Note 2: The [Edit...] button on the comparison report dialog allows you to modify formatting and layout of fields inside the report template and save it as a new one.  Technically, you can do this, but the feature is not supported You do any changes at your own risk and, unless you are very careful, it is likely that the modified template won't work.  Still, here are a few hints for the brave ones:

· When saving the new template, always save into the default template directory.  Name the new file "your-report-name.DD.FR3". The ".DD" part is mandatory, the template editor won't put it automatically and without it your template won't be found.
· Templates for schema reporting and for data reporting are very different. Mixing them up will lead to errors.
· Never change names of any components in the template and don't remove any components: most of them are referred from the program, by names.  Basically all you can do is re-arrange the existing fields a little bit, adjust their sizes and text formatting (e.g. for a different page size).
· Template fields for particular database columns are generated dynamically. Their positions are determined by placeholder fields named rmColumnHeader and rmColumnValue (under "Compared Data" header).  You should be especially careful with those.

See also the topic on schema reports for additional information.

   
Converted from CHM to HTML with chm2web Standard 2.85 (unicode)