The kind folks at FxCop a released a new point release of FxCop. Here are the details. Note that FxCop will be incorporated as a fully integrated static code analysis tool (great link) in Visual Studio Team System.
One of the most frustrating features of T-SQL versus PL/SQL was always that nested scripts and command line variables were not defined. This made native “build from scratch” database scripts impossible to write in a straight forward manner. One was left with either using SQLDMO or having a script template and a preprocessor to build the scripts on the fly.
In fact, the latter is the approach I took for one former client. I defined an XML vocabulary for sequencing definable groups of SQL scripts and a token replacement scheme to approximate command line variables and pseudo-variables. Like WSH all over again. No fun...and now, no longer necessary!
Having been a version control manager for several years, I am a strong advocate of “build from scratch” databases rather than what I call “sourdough” database builds, where you have an “all the cooks in the soup” development database that you clean and copy using “Backup/Restore” or DTS. Of course there are diffing programs and code you can write to automatically shove new database objects to a version control system. I don't think it's wise to play fast and loose with, what I consider, the most valuable part of your code base.
Now databases can be bootstrapped using the standard SQL Server 2005 tool-set via SQLCMD. Sweet!