SQL errors and warnings

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.