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

Options / Comparison / User-defined types

Top  Previous  Next

opt_UDTAlthough this page of the dialog should be rather self-explaining, let's consider two examples of the situations which these two settings control.

Do changes in UDF make difference? Suppose you use some EmployeeID in various tables throughout the database. The ID is just an integer and so it is defined in the older (let's say production) database: "EmployeeID int not null". However you wished your scripts to look nicer and in the new (let's say development) version replaced them with a new user-defined type: "EmployeeID TEmployeeID not null". The actual type has remained INT. Do you wish the Diff to show all such columns as changed and try to synchronize them?

Do changes in physical type make difference? Suppose both databases are now synchronized and define all such columns as TEmployeeID. Then for some reason you decide that numbers are not good enough and TEmployeeID must be CHAR(5) instead. You rebuild from scratch your development database with this new definition and now comparing with the production version again. Both version have columns defined via TEmployeeID, but the actual physical types behind them are different. Do you need the Diff show all these changes and try to synchronize them?

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