Index Maintenance Task in maintainace plan cannot be modified to set the maxdop parameter - by Alberto Morillo

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 755384 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 7/24/2012 9:17:03 PM
Access Restriction Public



I would like to suggest the option to set MAXDOP for an index maintenance task (rebuild index/reorganize index) when creating/modifying a maintenance plan.

On the following thread you will find evidence that index maintenance tasks may originate deadlocks when MAXDOP on the instance is set to a value greater than 1. 

With the option suggested above, users should be able to set MAXDOP to 1 and that option will take effect only for the index maintenance tasks, avoiding deadlocks without changing MAXDOP at the instance level.

Hope this helps.

Alberto Morillo
Sign in to post a comment.
Posted by Purvi [MSFT] on 4/17/2015 at 10:56 AM
Hi Alberto,

Thanks for taking the time to write us about this issue.

It is expected to be released with the next public SQL Server CTP.

Thanks again for reporting this issue and continued support in improving our product.
Posted by Alex [MSFT] on 12/28/2012 at 9:38 AM

Thank you for proposing new DCR we always looking forward to improve our product based on the customer feedback.

We will consider this feature as a part of our planning for the next major release.

Thank you for your help
Alex Grach [MSFT]