Y and N vs 1 and 0

I suspect the Microsoft SQL development and change teams must be overrun at the moment.
That’s the only thing I could think of when I saw this in sys.dm_server_services:
Since when did Microsoft start using uppercase Y and N instead of the usual 1 and 0?
It’s not a documentation error. How did that get through peer review and change control?

Leave a Reply