Microsoft have recommendations around setting
MAXDOP on various versions of SQL Server, but this (old) article raises some issues and recommends setting
MAXDOP = 1 generally for SQL Server 2005 and indicates that some of the issues aren't fixed in SQL Server 2008.
Is there any indication that here are still problems with
MAXDOP > 0 and are any DBAs out there not using 0 to reduce risks?