One thing worth pointing out regarding the February CU for Project Server, is that we made no changes to the database schema as part of this cumulative update, and this means no update in the Versions table either. One usual way to see which update you have loaded is to look at the Versions table in each database – but for the 4 Project Server databases you will still see the version from the December CU (even if you didn't load the December CU – remember these are cumulative – the clue is in the name - so we will have updated when loading the February CU with the December changes.
The result is that the Versions table will show 6524.5000 – the December CU version, and to see if February CU has been loaded you will need to look at add/remove programs or check the assembly version of Microsoft.Office.Project.Server.PWA.dll, which will show 6529.5000.
For the client you will see the version of Microsoft Office Project 2007 of 12.0.6529.5000 with SP2 DSO of 12.0.6425.1000).
My colleague Dragos has already posted this topic on the French Project support blog at http://blogs.technet.com/frenchpjblog/archive/2010/03/09/version-des-bases-de-donn-es-project-server-apr-s-l-installation-du-cumulative-update-de-f-vrier-2010.aspx and he also points out that you will see the Feb CU version in the Versions table of the Windows SharePoint Services databases – just not the Project ones. Thanks Dragos for posting and also for reminding me that this is a good thing to blog.
I should also add that Imma has blogged this info in German at http://blogs.technet.com/germanpsvrblog/archive/2010/03/09/sql-ermitteln-der-installierten-produktversion.aspx - thanks Imma!
In the next few days I hope to find time to start posting a few topics around Project 2010 and Project Server 2010, particularly some recently found ‘by design’ features that may catch out some upgraders from 2007.