kevin 20860 (4/4/2013)

---

Ok not sure If I've got it right but if I add "where a.left not in (select id from dbo.ufn_Split(c.path) )" after the Inner join it appears to...

If it did then I'd be well on my way to fortune and glory. Alas, that is not the case.

The article...

kevin 20860 (4/4/2013)

---

Dwain (or anyone!)

Is there any way to detect an prevent this crashing on a circular reference? I need to have it support a circular ref but using this...

Jeff Moden (4/3/2013)

---

I guess I understand the concern some folks have with the title but I personally don't see a thing wrong with it. If you're not aware of...

jasona.work (4/3/2013)

---

Depending on the time of day, either straight or filtered through ground-up and roasted...

So you're saying you can teach an old dog new tricks? 😛

Thanks Steve for editing...

Steven, tspade and all the others (Phil expecially for multiple visits :-)) that have chimed into this lively discussion, my thanks for both your time reading the article and contributing.

Jim - I do get very excited about new things...

vliet (4/3/2013)

---

We tried both the CTE approach and the AND clause on the WHEN NOT MATCHED BY SOURCE part to merge rows spanning only a certain period. The performance of...

the sqlist (4/3/2013)

---

If the bound errors happens than you will have to replace it with an EXISTS condition:

... and exists (select * from #test2 where id =t.id)

The author was kind...

Mike -...

mmahon (4/3/2013)

---

Hi Dwain -

I have a technical lack of understanding as to how the cte and Merge work together. Hopefully you can explain it to me. While...

R.P.Rozema (4/3/2013)

---

dwain.c (4/3/2013)

---

P Jones (4/3/2013)

---

As another MERGE fan I'd use

WHEN NOT MATCHED BY SOURCE AND (t.ID = s.ID) THEN DELETE;

in the original merge statement.

But I've no complaints about...

the sqlist (4/3/2013)

---

al_kessler (4/3/2013)

---

P Jones (4/3/2013)

---

As another MERGE fan I'd use

WHEN NOT MATCHED BY SOURCE AND (t.ID = s.ID) THEN DELETE;

in the original merge statement.

But I've no complaints...

Mike McIver (4/3/2013)

---

David is absolutely 10% correct.

The "hazard" is given here:

"Hastily, we consult MSDN"

and

"A quick scan of the article"

and

"Obviously this must be the ticket, so let’s give that...