Skip to content

Update set-arithabort-transact-sql.md #10367

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sommarskog wants to merge 1 commit into
base: live
Choose a base branch
from
Open

Update set-arithabort-transact-sql.md #10367

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/t-sql/statements/set-arithabort-transact-sql.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ When `ANSI_WARNINGS` is `ON` (the default), the setting of `ARITHABORT` has no f
> [!WARNING]
> The default `ARITHABORT` setting for [!INCLUDE [ssManStudioFull](../../includes/ssmanstudiofull-md.md)] (SSMS) is `ON`, while a client connection in an application defaults to `ARITHABORT OFF`. Even if there's no functional difference as long as `ANSI_WARNINGS` is `ON`, the `ARITHABORT` setting is still a cache key. Therefore, SSMS and an application both using their respective defaults, have different cache entries, and might get different query plans, making it difficult to troubleshoot poorly performing queries. That is, the same query might execute slower in the application than in SSMS. When troubleshooting queries with [!INCLUDE [ssManStudio](../../includes/ssmanstudio-md.md)], always match the client `ARITHABORT` setting.

For expression evaluation, if both `SET ANSI_WARNINGS` and `SET ARITHABORT` are `OFF` and an `INSERT`, `UPDATE`, or `DELETE` statement comes across an arithmetic, overflow, divide-by-zero, or domain error, the query inserts or updates a `NULL` value. If the target column isn't nullable, the insert or update action fails and the user sees an error.
For expression evaluation, if both `SET ANSI_WARNINGS` and `SET ARITHABORT` are `OFF` and an `INSERT`, `UPDATE`, or `DELETE` statement comes across an arithmetic error - overflow, divide-by-zero, or domain error - the query inserts or updates a `NULL` value. If the target column isn't nullable, the insert or update action fails and the user sees an error.

The setting of `SET ARITHABORT` happens at execute or run time and not at parse time.

Expand Down Expand Up @@ -233,4 +233,4 @@ GO

- [SET Statements (Transact-SQL)](set-statements-transact-sql.md)
- [SET ARITHIGNORE (Transact-SQL)](set-arithignore-transact-sql.md)
- [SESSIONPROPERTY (Transact-SQL)](../functions/sessionproperty-transact-sql.md)
- [SESSIONPROPERTY (Transact-SQL)](../functions/sessionproperty-transact-sql.md)