Set Max Degree of Parallelism at the Database Level - by DaveKBrown

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


5
0
Sign in
to vote
ID 622347 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 11/16/2010 12:33:00 PM
Access Restriction Public

Description

Currently, you can set the Max Degree of Parallelism at two levels.  At the server/instance level and at the query level.  We deployed an ISV application that the vendor insists that I set the Max Degree of Parallelism to 1 at the server level.  They believe it will help their application run better.  I told them no because the database is on my production server that is shared by other applications and those applications could benefit from parallelism.  I could set up a separate instance or set up a separate server to host this application's database, but that is a lot of overheard, plus the cost of licenses for a separate server, for a small database used by the application.

So, that being said, it would be great if I could set the Max Degree of Parallelism at the database level.  This would allow me to satisfy the ISV requirements and still have parallelism for the other databases that are hosted on the server. 
Sign in to post a comment.
Posted by Microsoft on 1/25/2012 at 3:46 PM
Thank you for submitting this suggestion, but given its priority relative to the many other enhancements we are considering, it is unlikely that we will actually complete it. And also, a workaround has been mentioned in the comments. As such, we are closing this suggestion as “won’t fix”. If you feel that this is worth reconsidering, feel free to respond to this message and we will take another look.


Thank you,
Eric Hanson
Program Manager
SQL Server Query Processing
Posted by Microsoft on 11/18/2010 at 9:27 AM
Actually, you CAN control DOP with Resource Governor. It is a setting on Workload group:
http://msdn.microsoft.com/en-us/library/bb895361.aspx

Create one workload group for the database, and you should be able to solve the problem this way.

Best regards,
Eric
Posted by Microsoft on 11/17/2010 at 5:54 PM
This is an interesting suggestion. We will definitely consider some solution to this issue for a future release.

Best regards,
Eric Hanson
Principal Program Manager
SQL Server Query Processing Team