Yes, but the SQL standards also have a BOOLEAN...

Sean Lange (7/21/2016)

---

drew.allen (7/21/2016)

---

Get rid of the ISNULL altogether. FOR XML automatically discards null expressions unless the XSINIL directive is specified.

SELECT DISTINCT STUFF(

(SELECT ', ' + t2.Name

FROM #Temp t2

where...

Get rid of the ISNULL altogether. FOR XML automatically discards null expressions unless the XSINIL directive is specified.

SELECT DISTINCT STUFF(

(SELECT ', ' + t2.Name

FROM #Temp t2

where t1.ID = t2.ID...

It's not clear how these results derive from your sample data: specifically, it's not clear why there are two rows for ER instead of 1, and it's not clear where...

kewlguy13 (7/15/2016)

---

Thanks Drew for the comments!

If I had to design the Junk dimension with these values, what do you suggest.

What would be Junk Dimension structure?

Logic: I was thinking about CROSS...

kewlguy13 (7/15/2016)

---

Thanks Guys for the quick response!

Looking at the target table structure, I could see that Cross Join doesn't fit. That's where I was confused.

I will try with the EAV...

Jabba1963 (7/15/2016)

---

My problem in trying to apply (excuse pun !!) the CROSS APPLY approach from details in the article using one table - where I have many... basically its confusing...

Your design is for an EAV table, not a junk dimension. A junk dimension is derived from the Cartesian product of your attributes so it would look more like

JunkID

SubscriptionStatus

CustomerStatus

PaymentDesc

Document

CaseType

TransportedTo

Obviously,...

I found a solution that seems to perform very well given certain pre-conditions.