Can you generate and post a couple of execution plans? That will help show what's happening under the covers on your system, with your data.

This will help if you haven't...

Personally, C#. It's what all the cool kids seem to be doing these days, so it's more likely to allow you get jobs and/or recruit people into the jobs you...

Fraggle (12/17/2008)

---

Thank you both for the reply.

Gail, are there any articles you would recommend on using server side traces?

Grant, you are correct. I did fail to mention...

Google & BOL aside, they've managed to find their way to this site, navigate to the forums, type their question.... Didn't even a one of them look up & to...

Yeah, Ian, that sounds like a good approach. I was thinking more or less the same thing, but didn't put in as clear as manner as you just did.

OK. Now that I'm seeing the full graph at last, I'll sound a little less foolish (but only a little). I'm seeing you running two updates, in different orders, the...

Ah sorry, different issue, different post. My mistake.

BTW, it's always helpful, but hardly necessary, that if you answer a question you posted, go ahead and post the answer. It'll not...

I don't have the answer, but you might want to post the question over in the 2008 forum. If people aren't monitoring both, they may not see this.

Also, if this question is related to this post:

http://www.sqlservercentral.com/Forums/Topic621088-145-1.aspx

You really shouldn't post multiple times because it just diffuses the conversation, making it harder for people to help and duplicating effort.

Simply updating 46 columns should not cause a deadlock. This would cause blocking, as one resource would have to wait on another while it's update completed. You have other processes...

Are these queries part of a bigger set of commands? Nothing there indicates why you'd receive a deadlock. You need to look at the statements prior to these two to...

Or edit the post... that works too.

Most of it is not displaying. You should try zipping it up and posting it as an attachment.

To add to what Gail says, I'd also suggest, that when you're not troubleshooting deadlocks, capturing the Start command is unnecessary. Usually getting RPCComplete and SQLBatchComplete covers just about everything...

You can use the OR construct or even COALESCE

WHERE SomeValue = COALESCE(@Param,SomeValue)

But the OR constract and the COALESCE construct aren't going to perform terribly well because either one will cause...