Inconsistent IgnoreWhitespace = false behavior in SQL Compare
SQL Compare in some instances trims the whitespace characters at the beginning and end of object definitions. While in other instances it takes them into account.
For example when comparing objects directly with IgnoreWhitespace = false it will show the whitespace differences at the end of the object being compared. (See attached screenshot of single direct object comparison)
However, when you generate a script to based off this comparsion the script does not include the expected whitespace changes.
SQLServer considers whitespaces at the end of object to be part of the object definition. SQLServer will include any whitespace characters until it encounter EOF or a GO statement. You can see these whitespace characters via the sp_helptext function. (see attached screenshot)
SqlCompare should be consistent with SQLServer definitions when IgnoreWhitespace = false for all functionality including script generation.