I can\'t figure out what\'s wrong with the following code, The syntax IS ok (checked with SQL Management Studio), i have access as i should so that works too.. but for some
As Travis and others have mentioned, other things can also cause extra output that SET NOCOUNT ON will not prevent.
I had SET NOCOUNT ON at the start of my procedure but was receiving warning messages in my results set.
I set ansi warnings off at the beginning of my script in order to remove the error messages.
SET ANSI_WARNINGS OFF
Hopefully this helps someone.