From 80104f7e042cb4bfb62915ae36961c2b4969e12f Mon Sep 17 00:00:00 2001 From: sommarskog Date: Fri, 24 Jul 2026 23:43:18 +0200 Subject: [PATCH] Update set-arithabort-transact-sql.md Small fix to a passage that did not really parse. --- docs/t-sql/statements/set-arithabort-transact-sql.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/t-sql/statements/set-arithabort-transact-sql.md b/docs/t-sql/statements/set-arithabort-transact-sql.md index 92b59b7181e..4346a58ad1d 100644 --- a/docs/t-sql/statements/set-arithabort-transact-sql.md +++ b/docs/t-sql/statements/set-arithabort-transact-sql.md @@ -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. @@ -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) \ No newline at end of file +- [SESSIONPROPERTY (Transact-SQL)](../functions/sessionproperty-transact-sql.md)