Tom -

what kind of output were you expecting?

Try this on for size:

Select r.value('./Name[1]','varchar(20)') as Name,

r.value('./Address[1]','varchar(100)') as Value

From @X.nodes('/Customers/Customer') as x(r)

I'm thinking this...

I think the issue would be whether the implicit CAST will continue to be supported, or if the date values will continue to be stored as floating points where the...

I should have worded that as a 10,000 row GROUP. Making an assumption about the size of your groups is really dangerous. All you would need is one...

I'm wondering if you could wrap that in a recursive CTE with OPTION (MAXRECURSION 0)? Hmm, and then just rename it CTEHardWareKiller and sit back an pick up the...

Sure it can, and as a matter of...

(G Bryant McClellan:) Well - now I'm thinking you are confusing the primary Key and clustered key functions. They are not the same and do not necessarily have anything...

It sounds to me that you're making this extra complicated by not giving yourself enough columns in your tbl_big staging table (I'm assuming it's a staging table).

If you were to...

jaholbrook (2/11/2008)

---

identity columns are like the fast food of the database world.

..."Super Size Me" ring a bell.

Basically a lack of understanding on the upfront work involved in modeling. Does...

(I'll skip the quoting since we're now up to quoting each other 4 levels deep....:))

No - of course not - it wouldn't know what kind of join you want. ...

Arthur -

Picking the name of the table or view from the drop down is equivalent to select * from MyTableOrView. In the same way that that's bad...

If you want to leverage XML in reporting services, you should probably be looking at pre-processing whatever you had in mind, and storing it in XML data columns. the...

TheSQLGuru (2/8/2008)

---

Are you speaking of my presentations? I have quite a few events coming up, including the Raleigh and Alabama Code Camps. Suppose you must be talking about...

I wouldn't restrict it. It's where SQL server stores its activity. If you limit it and for some strange reason your log hits that size before your log...

Caffeine boost just kicked in. I think this is the XML trick applied to your case:

SELECT pidt.primary_id,

pit.prtype_id,

pit.prtype_name,

STUFF((SELECT ', ' + LTRIM(RTRIM(pit1.secondary_id))

FROM partyInfoTable pit1

WHERE pit1.primary_id = pidt.primary_id...

I'm currently one state north (Raleigh), but I have family around Atlanta.

Careful - you never know when some crazed carolinian might show up demanding beer:)