Posted by jim_geissman on 04/06/06 17:12

Re SET NOCOUNT

My experience yesterday:

a) default state is row count echo, e.g. "(1257343 row(s) affected)"
b) set nocount on stops those -- e.g., during a script that does a lot
of inserts
c) while nocount is on, the echo is: "Command(s) completed
successfully." Once for each block of commands rather than
individually for each insert/update/etc query
d) set nocount off should cause row counts to reappear -- a way to
confirm queries are working
e) "Command(s) completed successfully." persisted after set nocount
off -- have to use other means to confirm what happened

[Back to original message]