Help me in this question

Question

Post reply

Help me in this question

yousef.am

Newbie

Points: 7
More actions
December 14, 2008 at 1:58 am

#195037

I need to know what the following statement does:
set nocount on;

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Adi Cohn-120898 SSC-Dedicated Points: 33944 More actions · Answer 1

It suppresses the message about the number of of records that were effected by the SQL Statement.

Adi

--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Grant Fritchey SSC Guru Points: 398911 More actions · Answer 2

And you use this to reduce the number of calls back and forth between the stored procedure and the application calling it.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

Mr James Howard Ten Centuries Points: 1158 More actions · Answer 3

When SET NOCOUNT is ON, the count (indicating the number of rows affected by a Transact-SQL statement) is not returned. When SET NOCOUNT is OFF, the count is returned.

James Howard

Steve Jones - SSC Editor SSC Guru Points: 736602 More actions · Answer 4

People usually do this in stored procedures to be sure extraneous messages are not necessarily sent to the client.

Typically this doesn't have a huge effect.

Jeff Moden SSC Guru Points: 1004434 More actions · Answer 5

yousef.am (12/14/2008)
I need to know what the following statement does:
set nocount on;

Save yourself some huge amounts of time in the future... learn to use Books Online, the "help system" for SQL Server. Like good spaghetti sauce, "It's in there". 😉

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Jeff Moden SSC Guru Points: 1004434 More actions · Answer 6

You'll also find that it's absolutely necessary to keep from getting "false returns" in a GUI that may be interpretted as error messages, especially on triggers.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)