I totally agree that DB Ghost is a terrific product that is filling a void in the SQL source control management area. The only caution I would add is over simplification on the real world scenarios that are rarely found in actuallity. The "Hello World" examples that we most often see from Microsoft and reviews usually do not apply in most cases. This would be no exception.

You should carefully consider the impact to your current processes. If you have a scenario that does not fall into the "Hello World" examples, what is it going to take to really implement a new product? How does this impact your development team? Your packaging group? Testing? (QA)

If your production databases are as suspect as most, are their additional steps that you will need to take during the transition period? Are these databases internal or external? If external, you may have to add features to your upgrade process.

Does your management and development team support the new process 100 percent from the beginning or will the process be implemented in stages? The work required could be much greater initially when trying to integrate new and old processes.

DB Ghost also has some terrific features that in order to take advantage, you need to allocate the proper resource time. Features such as the Software Development Kit and the scipting tool. What this software will help you accomplish long term is well worth the effort but it is not an overnight transition.