That's what I get in 2019. Don't have a instance of 2017 loaded to see if it's the same.

Literally just the way it's presented in the question. Either with a scalar function, or in a longer script with a pre-built table of replacements.

That's really very clever. I can see making some code much cleaner using this instead of nested REPLACE operators.

How many of us had SSMS open in front of them when they read this question? I knew the answer, but I wondered if right-clicking the query window had a...