Oh, then you want:

OUTPUT inserted.IDColumn AS NewID,
       deleted.IDColumn AS OldID

Ahh, does mean that the old newsletter links are dead though. That's actually far from ideal I have quite a few bookmarked/saved; so that's disappointing 🙁

Think this is actually a great move by Microsoft to get people, like MVPs, to be able to help out with the contributions on BOL. I've made a few myself...

Is this not as simple as:

INSERT INTO {YourTable} ({List,of,columns,goes,here})
OUTPUT inserted.{OldIdColumn},
       inserted.{NewIDColumn}
VALUES ({Values,to,insert,go,here});
/* --Or, if a SELECT statment
SELECT {List,of,columns,goes,here}
FROM YourOtherTable YOT
 ...

Honestly, pasting from SSMS wasn't working at all for me. Here's hoping it is now:

WITH N AS(
    SELECT 1 AS I
   ...

• This reply was modified 7 years, 2 months ago by Thom A.

Will there always be 5 parts? Could there be more, less, an unknown number?

No, that isn't what it'll do. If the day is monday the the start date will be the sunday and the end date the monday. If it is Tuesday it'll...

Guessing you have SSDT 15.8.1 or later installed? That removed support for SQL Server 2012. You need to use SSDT 15.8.0 or earlier.

Why are you executing it 40,000 times? Why not once with a GROUP BY clause?

You're explicitly defining the value from your xml as a varchar(19), and you're stating that the column is a varchar as well. Perhaps there is a trigger on your table...

I have been using containers at home to spin up SQL Server, but I am still actually installing it. I now solely use Ubuntu at home, and specifically my normal...

Seems you know what you need to do, you want to group the data, so have you had a look at the GROUP BY clause and