sqlsql-servert-sqlnocount

Semantics of sql NOCOUNT

This is a minor question regarding the usage and semantics of the NOCOUNT statement. I've seen it used a couple different ways and I want to know what is actually required or not.

I've seen it listed on MSDN with the trailing semicolon and GO statement like such:

SET NOCOUNT ON;
GO

and I've seen in without the trailing semicolon:

SET NOCOUNT ON
GO

and I've seen it without the GO statement

SET NOCOUNT ON

I realize that the GO simply signals the end of a batch, but should this be called in order for the NOCOUNT to take effect?

And what is the point of the semicolon?

Solution

  • A semicolon ends the current SQL statement.

    To the best of my knowledge, it isn't needed after SET NOCOUNT ON.

    You should not need 'GO' to have NOCOUNT take effect, though I'm less certain of that.