• Jeff Moden (6/29/2016)


    GilaMonster (6/29/2016)


    Jeff Moden (6/28/2016)


    Steve Jones - SSC Editor (6/28/2016)


    Jeff Moden (6/25/2016)


    From the Article:


    “This doesn’t work like it used to.”

    While I agree that it probably has fewer bugs that previous releases, this one broke a whole lot of code where people used XML for purposes of concatenation according to some.

    You'll have to provide a reference. I haven't seen this at all, nor can I find anything in searches. Perhaps I'm not looking in the right places, but I'd like to see a repro before I believe this.

    http://www.sqlservercentral.com/articles/STRING_SPLIT/139338/

    See the section under "Creating Large Scale Test Data"

    Where specifically? The only comment I can see in that section that refers to something broken is the CE changes to 2014 which changed the plan and resulted in non-random data.

    The code block immediately above that comment. If you run it in 2012 or less, works as expected. According to Wayne, if you run it in 2014 or better, it still runs but not as expected. Instead of making unique rows, it makes identical rows (which I lovingly refer to as "grooved data").

    OK, but I'm not sure that broke a whole lot of code. Certainly could be a regression, but there's a workaround. This also is a 2014 break, or did you note that earlier? This isn't a SQL 2016 issue, and not sure it's more than a change in behavior rather than something not working.