Here's the updated post that actually takes advantage of JSON.  No need for TRIM() or STRING_SPLIT() functions because the source is in a proper JSON ARRAY format.  Again,...

All good reasons for why I have a serious dislike for XML, JSON, and a couple of other things when it comers to SQL.

Thanks for the info, Jeffrey.  And, I'm...

Damn!  Awesome catch, Jeffrey! ...

@Ric,

Ok... so I'm only 14 years late in seeing this the first time. 😀

I've not needed to work with JSON up until now.  It's gotten out of hand in our...

Heh... you posted while I was writing the code.  Thanks, Jonathan.

Here's the updated post that actually takes advantage of JSON.  No need for TRIM() or STRING_SPLIT() functions because the source is in a proper JSON ARRAY format.  Again, this eliminates...

• This reply was modified 2 years, 7 months ago by Jeff Moden. Reason: Add the conversion to INT per Jeffrey Williams excellent tip below

p.s.  I seem to remember a way to do this directly with JSON and not have to do the STRING_SPLIT() and TRIM() things.  I'm looking for it.

[EDIT]: DON'T USE THIS METHOD.  I left the post here to show you that I'm actually quite the rookie at JSON.  There's no need for the complexity of the...

Interesting article, thank you.  The error returned 1 for the state.

Our dev team updated the code that generates the EF query, and that has resolved the problem (so I...

Thank you for the feedback!

  Interesting.   Thanks for the feedback, Phil.

The last group of data in your example data looks like this...

,(2,7, 210,1)

,(2,8, 211,1)

,(2,9, 212,1)

,(2,10,212,-1)

,(2,11,211,-1)

,(2,12,212,-1) --<---<<< LOOK HERE!

Shouldn't that last line have an Order_ID of 210 instead...

Deleted... I misread the problem.

Didn't they interview him?  Given the choice,...

Jeff, I honestly don't remember what my answer was.  but I'll add this:  Today my answer would be :

"If I ever get out of this silly-assed meeting I'll go...