This article is really too simplistic. As others have pointed out the idea of refreshing the development DB nightly is a non runner with true development as it means any development schema changes etc would be lost and need recreating nightly too - though it should be refreshed at theend of each project/rollout.

A key tip would be to use some schema comparison tool before rollout to compare the dev schema back to the live one (there are many tools advertised via this stie that can do the job but even a scripting out of all objects via Enterprise Manager and WinDiff should show you the changes - then these need to be checked against the schema change script the developers have produced to check they haven't missed anything).

Oh - and always use scripts for schema changes - GUI in enterprise manager is easy but not trackable in the same way as a source controlled set of change scripts is.