NOCOUNT Performance Differences

Aaron Bertrand looks into whether SET NOCOUNT ON provides a performance improvement:

For years, I had been operating under the impression that SET NOCOUNT ON; was a critical part of any performance strategy. This was based on observations I had made in, arguably, a different era, and that are less likely to manifest today.

Check out the comments as well.  This is an interesting conundrum as there’s a lot of ingrained knowledge that SET NOCOUNT ON is faster (and I admit that I thought I remembered it being the case when going through loops), but people have had limited success in coming up with a scenario in which it makes an appreciable difference.

Related Posts

Separating Data And Log Files

Brent Ozar looks at an old chestnut: So it’s time for a quiz: If you put all of a SQL Server’s data files & logs on a single volume, how many failures will that server experience per year? Bonus question: what kinds of data loss and downtime will each of those failure(s) have? If you […]

Read More

47 Incorrect Deployment Assumptions

Brent Ozar has a list of 47 assumptions regarding database deployments that turn out not always to be true: 30. The deployment person wouldn’t dream of only highlighting some of it and running it. 31. The staff who were supposed to work with you during the deployment will be available. 32. The staff, if available at […]

Read More

Categories

February 2016
MTWTFSS
« Jan Mar »
1234567
891011121314
15161718192021
22232425262728
29