Max Degree of Parallelism for SQL Server 2008 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.


Six Reasons You Should Be Nervous About Parallelism


Is there any indication that here are still problems with MAXDOP &gt; 0 and are any DBAs out there not using 0 to reduce risks?
This should be set with respect to your system baseline, you have to balance it with your CPU + COST Threshold for parallelism.

for example, i was using the configuration of maxdop=0 when i realized that i have an high number of worker threads. once i reset it to 5 and cost threshold to 50 everything was fine.