Jeff Moden (2/9/2014)
TheSQLGuru (2/9/2014)
Jeff Moden (2/9/2014)
TheSQLGuru (2/9/2014)
Please provide several sample sets of data and the corresponding table output you expect (with column data types). That's JSON, yes?THAT's JSON? Shoot... that's just as bad or worse than attribute based XML. We need a few more "standards" for passing simple data. 😀
I personally feel that JSON is MUCH worse than XML (and I frickin' HATE XML, so that should tell you something), but alas JSON has taken over and we are just going to have to learn to make the best of it.
Ah, my friend. I've found a kindred spirit. You've made my day and maybe the whole bloody week! 🙂
Make that three against JSON.
Had a project once where they required us to convert JSON to XML, then normalize and import into the database, then believe it or not - reconvert the normalized data into a JSON string to also be stored.
They didn't like that we shortcuted and just passed the JSON string to the database rather than converting it from normalized back to JSON. But they learned to accept it (they being those who came up with the stinking requirement).
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events