Hi,

Yes, corrected the index for ENGINE_ENTITIES

CREATE TABLE [dbo].[ENGINE_ENTITIES](

[ID] [bigint] IDENTITY(1,1) NOT NULL,

[CREATED_DATE] [datetime] NULL,

[ENTITY_ID] [varchar](255) NULL,

[ENTITY_TYPE] [varchar](255) NULL,

[PROCESS_INSTANCE_ID] [bigint] NULL,

[STRING_DATA] [varchar](255) NULL,

[UPDATED_DATE] [datetime] NULL,

[XML_DATA] [text] NULL,

PRIMARY KEY NONCLUSTERED

(

[ID] ASC

)WITH...

Hi,

Thanks for pointing that. I ensured my connection String has

sendStringParametersAsUnicode=false

To be double sure I also cleared my current cache with

DBCC FreeProcCache

DBCC DropCleanbuffers

and ran the Application again.

The in the deadlock...

Hi,

Pls find attached the sqplplan(s) generated by the query you have provided.

Yes,

sendStringParametersAsUnicode=false

was added to the connection String.

I think hibernate is passing the arguments as varchar and JTDS driver is converting it to NVARCHAR.

I also tried creating table with datatype NVARCHAR -...

Structure of ENGINE_ENTITIES

CREATE TABLE [dbo].[ENGINE_ENTITIES](

[ID] [bigint] IDENTITY(1,1) NOT NULL,

[CREATED_DATE] [datetime] NULL,

[ENTITY_ID] [varchar](255) NULL,

[ENTITY_TYPE] [varchar](255) NULL,

[PROCESS_INSTANCE_ID] [bigint] NULL,

[STRING_DATA] [varchar](255) NULL,

[UPDATED_DATE] [datetime] NULL,

[XML_DATA] [text] NULL,

PRIMARY KEY CLUSTERED

(

[ID] ASC

)WITH (PAD_INDEX =...

Hi,

yes, there is only one transaction in each of the sessions.

The deadlock I have on table NODE_INSTANCE_LOG is gone now after making the following change

/* Deadlock Fix */

CREATE TABLE [dbo].[NODE_INSTANCE_LOG](

[id]...

I am attaching the Deadlock report and the XML file with the execution plan (as zip files)

Would appreciate if some one can help me analyse it.

I have updated my connection string to

jdbc.url=jdbc:jtds:sqlserver://XXXXX:1433/XXXXX;instance=MSSQLServer;sendStringParametersAsUnicode=false

I am still facing the deadlock.

Can confirm that 2 queries causing deadlock are #select#.

I am not able to find the actual values that...

Hi,

I have read the link

http://technet.microsoft.com/en-us/library/ms378988.aspx

for sendStringParametersAsUnicode=false.

I see no relationship between this parameter and indexes not being used.

Can you pls clarify?

regards

D

Correct to my earlier observation. Its not a select/update that's causing the deadlock but its a select/select

I am pasting an extract from the Tracer

<deadlock victim="process6a9048">

<process-list>

<process id="process6a9048" taskpriority="0" logused="15888" waitresource="KEY: 6:72057594142588928...