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

SQL errors and warnings

Top  Previous  Next

Some errors that MS SQL Server reports are actually just warnings. At least, they should not prevent you to proceed executing the rest of script. The most prominent example is when you CREATE PROCEDURE which refers to some undefined object. The server does create it, but then complains that it "Cannot add rows to sysdepends... The SP is still created". Another example is when you try to DROP an object which is not there - this produces an error, but the result is as good as if the object were actually dropped.

The correct reaction in such situations would be to record a warning message and proceed to the next statement, rather then stopping at the failed statement.  So AdeptSQL Diff uses a configuration file which lists error codes for all such exceptions.

The file is called MSSQLIgnoredErrors.cfg and located in the installation directory of the program. It contains one error number per line, the number must be the first non-blank token on the line (leading blanks are permitted). Any non-digits after the number are considered comments, lines starting from a non-digit or blank lines are ignored. There is no special user interface to modify this files; if you need to do so, do it in a text editor.

 

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