|
|
Posted by Erland Sommarskog on 10/02/00 11:44
(jim_geissman@countrywide.com) writes:
> 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
So you mean that if you had:
insert #h (a) values (12)
go
insert #h (a) values (12)
go
You got "Command(s) completed successfully." twice? I have never seen that.
> 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
Maybe there is some way to get Mgmt Studio to lose control, so you
could this behaviour, but I think you need to find a reproducible
scenario, for a bug report to be meaningful.
Those (1257343 row(s) affected), were they just instered, or were they
from a SELECT that was sent to Mgmt Studio?
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|