Grim as that was, it's worth noting it's referring to issues with SQL Server 6.5 and 7 over 10 years ago. As the current release is v10.5 (2008R2) and we're sch

Grim as that was, it's worth noting it's referring to issues with SQL Server 6.5 and 7 over 10 years ago. As the current release is v10.5 (2008R2) and we're scheduled to next year see v11 (2012) I would suspect the relevant problem tickets have been resolved...