Suggestion for SQL Compare: Useful error messages

samjones11samjones11 Posts: 14
edited March 13, 2009 11:01AM in SQL Compare Previous Versions
As you can see in this thread: http://www.red-gate.com/MessageBoard/vi ... 1164#31164

SQL Compare is not working out for me (so far).

(Hey, that is what demo versions are for, right? <g>)

Anyway, an observation:

1) When SQL Compare throws an error, or has an issue, it does not specify the file(s) that are problematic. This is very frustrating, and, frankly, weak.

Example:
When it finds two CREATE TABLE FOO statements, it should say something like:

"The SQL files in directory <dir> would return errors if run against a SQL Server, so SQL Compare is unable to process them. Specifically, there are two CREATE TABLE FOO statements, one in <file1> and a second in <file2>.

Please correct the SQL so that it would run properly against SQL Server, and SQL Compare will be happy to process it."


2) It would be nice of the process were more granular. For example, say there are two CREATE TABLE FOO statements. It would be great if SQL Compare would say: "Unable to process element CREATE TABLE FOO. This result will be ommitted from the results.
[OK, continue without FOO] [Stop, user will fix FOO and retry this operation]


Thanks!

Comments

  • Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    Thanks for your suggestion.

    When registering scripts folders, duplicate objects still leave you without enough information to fix the problem. However, version 8 has added a special error dialogue box for registering scripts folders, which will highlight any syntax errors and also point out the script file so that you can easily identify and edit it. It's only the specific circumstance where you have the same object defined in two different files that causes some confusion. We can look into this for a future version, definitely.
Sign In or Register to comment.