You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SQL Server Name Convention and T-SQL Programming Style.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -555,7 +555,7 @@ Recommendations from Microsoft: [Stored procedure Best practice][11]
555
555
- The procedure or function should begin with parameters checks (see example below)
556
556
- Create `sp_` procedures only in `master` database - SQL Server will always scan through the system catalog first
557
557
- Always use `BEGIN TRY` and `BEGIN CATCH` for error handling
558
-
- Use `SET NOCOUNT ON;` for stops the message that shows the count of the number of rows affected by a Transact-SQL statement and decreasing network traffic.
558
+
-<aid="nocount"></a> Use `SET NOCOUNT ON;` for stops the message that shows the count of the number of rows affected by a Transact-SQL statement and decreasing network traffic.
559
559
More details [here](https://www.red-gate.com/hub/product-learning/sql-prompt/finding-code-smells-using-sql-prompt-set-nocount-problem-pe008-pe009) and [here][11].
560
560
- Do not use `SET NOCOUNT OFF;` because it is default behavior
561
561
- Use `RAISERROR` instead `PRINT` if you want to give feedback about the state of the currently executing SQL batch without lags.
0 commit comments