You may have already heard of an issue with the August CU for WSS and potentially problems when re-attaching content databases after application of this cumulative update. It is documented on Stefan Goßner’s blog at http://blogs.technet.com/stefan_gossner/archive/2009/09/14/important-be-careful-when-installing-wss-august-cumulative-update.aspx?CommentPosted=true#commentmessage
One comment on Stefan’s blog asks about Project Server databases, so I added a comment there (which isn’t live at the time I write this) and will repeat for reference here.
The Project Server 2007 (or 2010) databases are not content databases and there isn’t really the same concept of “attaching” them as there is for WSS (or MOSS or SharePoint 2010) Content databases. We do use the term DB attach for Project, and you will hear this more for 2010 and it usually refers to restoring the 4 Project Server databases and provisioning a new PWA site. This process will upgrade the Project Server databases to the latest schema installed on the farm, in the same way that PSConfig (the SharePoint Configuration Wizard) will update the schema as one of the steps after applying a Service Pack or Cumulative Update. You should never detach the Project Server databases during the application of an update (I understand this can be a common practice with very large WSS Content databases).
And the good news for Project Server 2010 is that we will support a 5 DB Attach process where you can move the content DB and the 4 Project Server DBs between farms and provision a new PWA – WITHOUT LOSING YOUR WORKSPACES and without the need for stsadm exports and imports. This is very cool! More on this later – but thought I’d drop it in as it relates to the topic.