sorry to say, but your question is bogus. I just ran it on my SQL 2008 instance and received no row(s) effected message at all.

default settings. Doesn't even matter if set nocount is off/on. And I tested it with SQL 2012 too. Same results.

The one thing that might be different is I'm using SSMS 2012.