It really does sound like recompiles either from causes within the code or due to changes in the data. Especially since it seemed to happen over time and somewhat randomly,...

I wish I had a contact or three at MS. I'd love to see this moved up the chain... I'm going to try contacting a couple of people.

It's still Visual Studio.

While GUID's can be a unique value, you didn't put a unique constraint on the key, so when combined with the other part of your where clause, you're probably getting...

It sounds like Steve nailed it in one.

We had a similar issue, waits for compiles, which lead to other waits for compiles, etc.

Our code was actually compiling due to changes...

Ummmm. That was strange. Where the heck did the execution plan go?

If I run this query, I can see it.

SELECT

p.*,

q.*,

...

A log file is a mechanism I'd only use from the application side. If you're capturing error information inside SQL Server, just write it out to a table.

The optimizer, along with a whole of the rest of the engine, was changed between 2000 and 2005. It's not at all surprising that you'll see different execution plans in...

There's not a good source for this information. Experimentation is how I'm getting by.

I can recommend three sources that can help, in addition to posting here (althouth only a...

F'ing lovely. Worked perfect. Thank you.

Now what the heck did you do?:w00t:

I think the frequency is also going to affect this. You would have to check often enough to catch the event as it occurs.

Different people do it different ways. You can control the transaction from the application, but you need to be very cautious about getting extraneous code in the way of the...

Sorry, I only posted part of the XML. It's the XML from an execution plan. Here's a section of the entire XML file (brackets replaced):

[ShowPlanXML xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Version="1.0" Build="9.00.3042.00" xmlns="http://schemas.microsoft.com/sqlserver/2004/07/showplan"]

...

OK. It ran, but it's returning null for all the values and that's wrong. A little more help please?

OK. I think I get why you're using the [1] twice in the first example, but what do the parenthesis do in the second?

Oh, and thanks for the help.