How to over come from deadlock in embedded SQL through C# in SQL Server 2014?

Question

0.00/5 (No votes)

See more:

, +

Hi All,

I am facing deadlock problem on Dispatching.PackageTrace table when below Embedded SQL is invoked through C# programming language in MS SQL Server 2014.

Below is the table design in Database:

CREATE TABLE [Dispatching].[PackageTrace](
[PackageID] [uniqueidentifier] ROWGUIDCOL NOT NULL,
[PartitionID] [numeric](26, 0) NULL,
[Conduit] [nvarchar](255) NOT NULL,
PRIMARY KEY CLUSTERED
(
[PackageID] ASC
)

IF EXISTS(SELECT * FROM Dispatching.PackageTrace WHERE PackageID = 'klaslndsskok230m')
BEGIN
UPDATE [Dispatching].[PackageTrace] SET [Conduit] = @Conduit
WHERE [PackageID] = 'klaslndsskok230m'
END
ELSE
BEGIN
INSERT INTO [Dispatching].[PackageTrace] ([PackageID] ,[PartitionID] ,[Conduit] )
VALUES (@PackageID, @PartitionID, @Conduit)
END

Suggestions really appreciated to over come from deadlock problem.

Thank you in advance.
--Raj

Posted 5-Nov-14 23:35pm

RajKuntal

Add a Solution

Comments

Sinisa Hajnal 6-Nov-14 5:55am

This seems legal, it's probably your code that locks the table.

ZurdoDev 6-Nov-14 7:34am

Use the ACtivity Monitor in SQL to see what is locking it.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

1337Architect · Answer 1 · 2014-11-06T16:59:00

Solution 1

Try to write your select query with a nolock statement. It should improve your situation a lot. Otherwise this part will block the entire table when running causing deadlocks.

SELECT * FROM Dispatching.PackageTrace (NOLOCK) WHERE PackageID = 'klaslndsskok230m'

Posted 6-Nov-14 16:59pm

1337Architect