Intermittently Getting below mentioned error during processing OLE DB error: OLE DB or ODBC error. Transaction (Process ID n) was deadlocked on thread| communication buffer resources with another process and has been chosen as the deadlock victim.
Cause: A deadlock is a circular blocking chain, where two or more spids are each blocked by the other so that no one can proceed.
You don’t have control over the Select Statement generated by SSAS Processing job (If you are not using Named Query in DSV), in that case you need take care of things from SQL Engine Perspective.
Here are few recommendations, which can reduce deadlock situation:
SET TRANSACTION ISOLATION LEVEL (Transact-SQL)
How To Monitor Deadlocks in SQL Server
I'm using SQL Server 2012 SP2 and AS also 2012 SP2
As you work in the AS team, do you know how to make the AS automatic generated query to append some hint in the end ?
I have a scenario where I could benefit from appending option ( HASH join) to force join type (SQL QO is incorreclty using loop join in some cases with lots of referenced dimension) at the end of the query ?
I can't use plan guides as the automalically generated query is bound to change in the future.
Also I'm having this problem of intra query parallelism deadlocks from time to time.