I would agree with the other comments, nice article but hardly best practice.  One thing that was not mentioned was the use of the Upgrade Advisor, which comes with SQL Server 2005.  I would highly recommend this prior to making an migration moves whatsoever as it provides you with a comprehensive list of tasks to be performed prior to migration, and once migrated setting the compatibility level to 90. 

For those looking for a resource on Partitioning in SQL 2005 Kimberly Tripp has a good paper on it.  http://www.sqlskills.com/resources/Whitepapers/Partitioning%20in%20SQL%20Server%202005%20Beta%20II.htm

I agree with Chris H regarding the use of CLR.  While I have not enabled it as yet I am certain that someone will present me with a strong enough business case where I will need to enable CLR in SQL.  I have not come to grips with a process for allowing developers to deploy, but one thing is for certain no code will be deployed until I have looked at the code and bless it. 

Microsoft is deprecating many commands as we know them today in SQL 2000 for better or for worse. Again running the Upgrade Advisor will assist greatly in the task of mitigating these issue.

John