It would have been useful also to alter the question to make it clear it was talking about SQL 2000, and not about SQL 2008. (Actually, I don't know for sure whether that particular bug has been fixed or not, but I imagine MS will have fixed it as they haven't updated the list of products to which the bug applies to include SQL 2005 or SQL 2008).