Data Dude's schema compare feature is a technical wonderment . . . when it works. It seems to be fine when comparing databases to each other. Unfortunately, when comparing a data dude "project" to a database created independently from Data Dude, Data Dude seems think that there is extra whitespace in its cached copy of the ddl for the database's view, function and stored procedure ddl. What's going on here? It turns out that Data Dude is very picky about what is considers properly written ddl definitions. Data Dude wants you to allow it to write all the ddl to the database! Thus if you have created your database objects in SQL Server Management Studio you'll have to resync going from the Data Dude project back to the database after importing the schema from the database--a full round trip. You should be careful about backing up, as always.
It's a shame such a great tool has such a lame bug.
Note: Data Dude is the nickname for the Microsoft project formally known as Visual Studio Team System 2008 Database Edition.
