Assume that you have a table that has columnstore indexes in Microsoft SQL Server 2014. When you run a parallel query that contains outer join operators against the table, an intra-query deadlock may occur, and you receive the following error message:
Transaction (Process ID n) was deadlocked on generic waitable object resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Note This issue only occurs when the max degree of parallelism (MAXDOP) option is set to greater than 1.
The issue was first fixed in the following cumulative update of SQL Server.
Cumulative Update 1 for SQL Server 2014 SP1 /en-us/help/3067839
Cumulative Update 8 for SQL Server 2014 /en-us/help/3067836
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Hotfix information A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.