SET NOCOUNT ON gives a performance boost to action queries by suppressing the "(n row(s) affected) message that results from running a query.
The performance boost is due to the few bytes of information that make up the "(1 row(s) affected)" message not being transmitted to the client application.
Communication between the database and the client application on a stand-alone machine will be as fast as it is possible to get.
For queries that retrieve data the performance boost will be less simply because the size of the "(1 row(s) affected)" message is small compared to the volume of data being returned.
In .NET applications an ExecuteNonQuery command returns the number of records affected by the operation. Set NOCOUNT ON means that the value that this call returns is always zero.
The performance boost is due to the few bytes of information that make up the "(1 row(s) affected)" message not being transmitted to the client application.
Communication between the database and the client application on a stand-alone machine will be as fast as it is possible to get.
For queries that retrieve data the performance boost will be less simply because the size of the "(1 row(s) affected)" message is small compared to the volume of data being returned.
In .NET applications an ExecuteNonQuery command returns the number of records affected by the operation. Set NOCOUNT ON means that the value that this call returns is always zero.
No comments:
Post a Comment