Friday, December 9, 2016

How to Suppress the "N Row(s) Affected" Output Message in SQL Server

Sometimes, when working with T-SQL scripts, you might want to skip the message "(N row(s) affected)" message.

You get this message when you execute T-SQL statements or stored procedures that they affect rows. To this end, SQL Server returns the number of records which were affected by the database operation you performed.

If you want to suppress this message, then you can use the "SET NOCOUNT" statement.

So, for example you can try something like this:

SET NOCOUNT ON;

-- Your query goes here

SET NOCOUNT OFF;

Below, you can see an example with screenshots that illustrates the above


Using NOCOUNT in SQL Server
Figure 1: Running a T-SQL Statement with the Default NOCOUNT Setting.


Using NOCOUNT in SQL Server
Figure 2: Running a T-SQL Statement After Setting NOCOUNT to ON.


The SQL Server and .NET Hub


Reference: The SQL Server and .NET Hub (http://www.sqlnethub.com)



[Ads]
Check out my latest eBook on SQL Server:
Tuning SQL Server - Ebook

Easily secure your SQL Server instances! Try out DBA Security Advisor!
DBA Security Advisor for SQL Server by SQLArtBits
DBA Security Advisor was developed by SQLArtBits. The tool was being carefully developed for an entire year and it contains comprehensive security checks and recommendations based on proven SQL Server security best practices. Feel free to download and use the Community Edition which is free and if you find it useful, you can consider upgrading to the Enterprise Edition!

Artemakis Artemiou [MVP]

Author & Editor

Artemakis Artemiou is a Senior SQL Server Architect, Software Developer and Microsoft Data Platform MVP. He is also an author, regular blogger, president of Cyprus.NET User Group and CY Country leader of INETA-EU. He is also the creator of DBA Security Advisor and In-Memory OLTP Simulator. Artemakis is a frequent guest author of worldwide well-respected online journals where he writes articles focusing on many SQL Server topics.

Reference: The SQL Server and .NET Hub (http://www.sqlnethub.com)

0 comments: