Home Forums SQL Server 2005 Administering Why does my query use MAXDOP = 0? RE: Why does my query use MAXDOP = 0?

  • March 11, 2014 at 8:36 am

    #1696011

    ChrisM@Work (3/11/2014)

    curious_sqldba (3/11/2014)

    sqlbuddy123 (3/10/2014)

    MAXDOP =1 means disabling the parallelism. That's why SQL Server doesn't consider parallelizing the query.

    That's why I couldn't see that in the execution plan you posted.

    --

    SQLBuddy

    Exactly, but my plan is using MAXDOP =0 ( 24 cores) in my case. Did you notice this?

    MAXDOP is not the same as "Degree of Parallelism" on the properties sheet of the INSERT operator. If you're still unsure, inspect the properties sheet of any of the index/table scans/seeks, which show "Parallel = False".

    Right, MAXDOP means the maximum it would go to based on Cost, in my case it should't go pass DOP =1 when cost is greater than 5, so cost is greater than 5 but it is using DOP = 0?