From cb074878d1c86522340c4e50e6e14142c9312587 Mon Sep 17 00:00:00 2001 From: sommarskog Date: Thu, 23 Apr 2026 23:41:10 +0200 Subject: [PATCH 1/2] Update alter-database-transact-sql-set-options.md Changed the required permission for DB_CHAINING based on observation: USE master go CREATE LOGIN alteranydb WITH PASSWORD = '))"?`?323Jdk' GRANT ALTER ANY DATABASE TO alteranydb go CREATE DATABASE chainer ALTER AUTHORIZATION ON DATABASE::chainer TO sa go EXECUTE AS LOGIN = 'alteranydb' go ALTER DATABASE chainer SET DB_CHAINING ON go REVERT go DROP LOGIN alteranydb DROP DATABASE chainer Also modified the language as such. It sounds funny to talk about a server permission "on the database". --- .../t-sql/statements/alter-database-transact-sql-set-options.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/t-sql/statements/alter-database-transact-sql-set-options.md b/docs/t-sql/statements/alter-database-transact-sql-set-options.md index 58088b5f3f1..60470ecd128 100644 --- a/docs/t-sql/statements/alter-database-transact-sql-set-options.md +++ b/docs/t-sql/statements/alter-database-transact-sql-set-options.md @@ -804,7 +804,7 @@ Controls whether the database can be accessed by external resources, such as obj > [!IMPORTANT] > The instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] recognizes this setting when the cross db ownership chaining server option is 0 (OFF). When cross db ownership chaining is 1 (ON), all user databases can participate in cross-database ownership chains, regardless of the value of this option. This option is set by using [sp_configure](../../relational-databases/system-stored-procedures/sp-configure-transact-sql.md). -To set this option, requires `CONTROL SERVER` permission on the database. +To set this option, requires the server-level `ALTER ANY DATABASE` permission. The DB_CHAINING option can't be set on the `master`, `model`, and `tempdb` system databases. From 2079e4072bb52962b1dfd54758ee7dbccf485d86 Mon Sep 17 00:00:00 2001 From: Randolph West MSFT <97149825+rwestMSFT@users.noreply.github.com> Date: Thu, 23 Apr 2026 16:49:18 -0600 Subject: [PATCH 2/2] Apply suggestion from @rwestMSFT --- .../t-sql/statements/alter-database-transact-sql-set-options.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/t-sql/statements/alter-database-transact-sql-set-options.md b/docs/t-sql/statements/alter-database-transact-sql-set-options.md index 60470ecd128..2df76ee593f 100644 --- a/docs/t-sql/statements/alter-database-transact-sql-set-options.md +++ b/docs/t-sql/statements/alter-database-transact-sql-set-options.md @@ -804,7 +804,7 @@ Controls whether the database can be accessed by external resources, such as obj > [!IMPORTANT] > The instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] recognizes this setting when the cross db ownership chaining server option is 0 (OFF). When cross db ownership chaining is 1 (ON), all user databases can participate in cross-database ownership chains, regardless of the value of this option. This option is set by using [sp_configure](../../relational-databases/system-stored-procedures/sp-configure-transact-sql.md). -To set this option, requires the server-level `ALTER ANY DATABASE` permission. +This option requires `ALTER ANY DATABASE` permission. The DB_CHAINING option can't be set on the `master`, `model`, and `tempdb` system databases.