If you have had or have the annoyance of Content Deployment errors, then I suggest having a look at:

http://blogs.msdn.com/sharepoint/archive/2008/07/15/announcing-availability-of-infrastructure-updates.aspx

As it stands, the ECM team released 2 infrastructure hotfixes in May 2008 to improve performance of Content Deployment. These have been rolled up into this hotfix. Check out the deployment guidelines at http://technet.microsoft.com/en-us/library/cc288269.aspx for WSS 3.0 and http://technet.microsoft.com/en-us/library/cc263467.aspx for MOSS 2007. The pre-deployment guidelines are really important. Such as how to handle web front end servers and the ever so important shrinking of database log files, permissions. I've seen a simple upgrade go pear-shapped due the the guidelines not being taken care of before hand.

Anyway... these hotfixes are rolled up into the July 2008 (KB KB951297 and KB951695)

Ensure you have already installed WSS & MOSS SP1. Looking at the SharePoint Team blog, it seems like additional features are added:

 Key updates for SharePoint Server 2007 include:

  • New Search features such as federated search and a unified search administration dashboard.
  • Several core fixes to Search to improve performance and scale.
  • Platform performance improvements and fixes.
  • Several core fixes to the publishing Content Deployment features to improve reliability.


Key updates for Project Server 2007 include:

  • Timesheets and My Tasks stability and usability improvements
  • Queue management user interface improvements
  • Project Server 2003 to Project Server 2007 migration fixes
  • Database performance improvements to enhance the cube building process and Project Professional Save/Publish scenarios


Key updates for Search Server 2008 and Search Server 2008 Express include:

  • Platform performance improvements and fixes since RTM

This is also a highyly recommended hotfix:

I'm still evaluating in the lab environment before going to customers but please remember, backup all farm databases before deploying any hotfixes. I'll keep commenting on this hotfix in our environments.