Check out the demo and discussion in the video TSQL: ARITHABORT ON and Query Speed. While it may seem like a harmless setting, this setting may affect our queries. We should be aware of how the application runs this setting. Also, when we test this setting on and off, we see different results. This is not incorrect, as depending on what we want the definition of various data measures to be, we may want those different results.
Keep these questions in mind when watching this video:
- How does this setting handle different mathematical operations?
- What is management studio fundamentally?
- What's the result of this setting on an off?
Check out the highest-rated Automating ETL course on Udemy, if you're interested in data.
If our transforms may involve data like these, we may want to consider these settings. As I point out in the video, I've seen this setting cause major conflict among developers/DBAs because each tend to blame the other for a query being slow. Wrong. Understanding this setting and how it affect queries may be the underlying issue.
YouTube | Automating ETL | T-SQL In 2 Hours | Consumer Guide To Digital Security