Thomas LaRock notes an oddity in SQL Server Management Studio and Azure Data Studio:
Anyway, I spend time trying to debug what is happening. I am able to manually set NOCOUNT on and off inside of T-SQL and see a count of rows affected returned (or not). I check and recheck everything I can think of and feel as if I have lost my mind. I’m starting to question how I ever became certified in SQL Server.
I mean, it’s a simple configuration change. This isn’t rocket surgery.
So I do what anyone else in this situation would do.
I turn off my laptop and forget about everything for a few days.
I’d never used this particular style of setting NOCOUNT on for a user (I would always enable it by session using SET NOCOUNT ON), so I’m not sure when certain tools started ignoring the user-level setting, but read the whole thing for maximum intrigue.