Tried one more. It won't be right either, but an effort was made.

Not defined in the original sets of posts. See why so many people are having trouble understanding what's going on?

How about something like this:

JoinedTable.account,

COALESCE(JoinedTable.mtd1,(JoinedTable.mtd2+i1.VALUE)

(SELECT...

Lynn Pettis (4/20/2012)

---

Just read Riya_Dave's latest post, just more of the same "I'll repost what I have already posted, maybe with a few minor but incomrehensible changes."

I wanted to say...

David Burrows (4/20/2012)

---

INSERT #temp3 (account,MTD,ytd)

SELECT t1.account,

COALESCE(t1.MTD,t1.m1 + account(@p1)),

COALESCE(t1.ytd,t1.y1 + account(@p1))

FROM #temp1 t1

LEFT JOIN #temp2 t2 ON t2.account = t1.account...

I am making an honest attempt to help out here.

First, I had to change your code because it won't run. Here are the updates:

CREATE TABLE #temp1 (

account INT,

...

I'm trying to understand, but I just don't get what you're doing. I'm sorry.

How do you get from this result set:

1001 23.45 34.32

1003 34.56 43.21

1003 null null.

To this result set:

1003...

The Dixie Flatline (4/19/2012)

---

Okay, I will apologize for bringing this up in the Thread. But I'm getting tired of writing private messages.

Yes, Gail, I was at the last Summit...

Brandie Tarvin (4/19/2012)

---

I am starting to do guest posts on my writing blog and I'm wondering if any of you Threadzian authors (who have done editing or writing on SQL...

Not knowing the internals of the multi-statement UDF, it's hard to know what to do about it, but those things are notorious performance pigs if you're dealing with more than...

Not seeing all the code & structures involved... not sure. Just guesses. Maybe moving to a tempdb creates a more up to date set of stats. Maybe moving to tempdb...

Also check the server settings, especially default connection settings. If one is using ANSI standard and the other is not, again, you might get different execution plans.

This is just because recruiters and HR departments only have a list of requirements, not actual knowledge. If you don't meet the list, you don't meet the list. The only...

It might be statistics that are out of date, but from the sounds of it, I'd want to be sure that the structures are identical, that the code in both...

Your statistics look to be off. You've got implicit data conversions on all your predicates, possibly causing all the scans, and it looks like you may have a multi-statement table...

It's absolutely a problematic approach to a JOIN. Functions like that means you can only ever scan the table.

The reason it might be erroring out so quickly is because...