As a software product evolves it is inevitable that the underlying database schema changes and you have to make sure any changes you make in the development cycle are made to all other database as the software is distributed. In all our products we include a database management module that propagates changes out to live databases and ensures the version of the software matches the database schema.
In the early stages of development though the schema changes made by designers and developers come fast and furious and it can be difficult keeping track of them and propagating them to other databases. At Paritor we have this problem and find it can be a long winded job comparing databases manually. There are tools out in the marketplace to analyse databases, show differences and even script any necessary changes but apart from the fact that they all cost money they all seem to be a "Sledge Hammer to Crack a Walnut". I therefore sat down the other morning and put together a simple utility to open up two database, analyse the differences and report on what it finds.
I wrote it as a WPF application, mainly because I wanted to use the WPF Document namespace to create the report and show it using the WPF Document Viewer. You could easily write it as a Windows forms and use System.Drawing.Print or even produce a Crystal Report.