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 / Scripting / General logic

Top  Previous  Next

opt_script_logicThis section of the Options dialog holds any options that affect the overall scripting logic, as opposite to the scripting of specific schema objects.

 

Transactions. To protect you from accidental loss of data, the Diff can put transaction code around any generated SQL. See also here for the details of how SQL Code Viewer supports transactions.

Always begin with USE ...  When you run scripts from within the Diff, the target connections are configured for specific databases, so explicitly choosing the database at the beginning of each script is not necessary.  However, if you plan to save the generated scripts and then run them elsewhere, always having a USE in the beginning may be convenient.

Use IF NOT EXISTS logic.    With this option enabled, every CREATE statement will be preceded by a check whether the object already exists.  Note that this option is used only in CREATE scripts (that is, when the Diff doesn't know what database the script will be executed against).  A difference script also can contain CREATE statements, but the "IF NOT EXISTS..." logic will not be included there.

NOTE: Starting from Diff 1.96 Build 98, the IF NOT EXISTS logic is implemented for all supported schema objects. Earlier versions only had it for tables and stored procedures.

 

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