Trace flag 8679 -- is it needed under SQL Server 2005?

Using SQL Server 2000 std. edition, I was bitten by the bug described in KBs 818671 and 289149. Query optimizer using Hash Match Team operators would sometimes fail. I added -T8679 at SQL Server startup.

Now that I'm upgrading to SQL Server 2005, is this trace flag still required

I see that "this was fixed in SQL 2000, SP1." However, I would like a more precise confirmation that this flag is no longer needed in SQL 2005. Sometimes, no news is not necessarily good news.

The error is intermittent, and at least partially dependent on data conditions not available to me for exhaustive regression testing (or else of course I would do that).

Any info, comments, etc. ... would be welcome.

Thanks ...

Tracy Slack