Skip to content
Open
Changes from all commits
Commits
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
3 changes: 0 additions & 3 deletions docs/t-sql/statements/create-database-transact-sql.md
Original file line number Diff line number Diff line change
Expand Up @@ -272,7 +272,6 @@ When `OFF`, the database can't participate in cross-database ownership chaining.
> [!IMPORTANT]
> The instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] recognizes this setting when the cross database ownership chaining server option is 0 (`OFF`). When cross-database 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 membership in the **sysadmin** fixed server role. The `DB_CHAINING` option can't be set on these system databases: `master`, `model`, `tempdb`.

Comment thread
v-dirichards marked this conversation as resolved.
#### TRUSTWORTHY { OFF | ON }

Expand All @@ -282,8 +281,6 @@ When `OFF`, database modules in an impersonation context can't access resources

`TRUSTWORTHY` is set to `OFF` whenever the database is attached.

By default, all system databases except the `msdb` database have `TRUSTWORTHY` set to `OFF`. The value can't be changed for the `model` and `tempdb` databases. We recommend that you never set the `TRUSTWORTHY` option to `ON` for the `master` database.

#### PERSISTENT_LOG_BUFFER = ON ( DIRECTORY_NAME = '*directory_name*' )

**Applies to**: [!INCLUDE [ssSQL17](../../includes/sssql17-md.md)] and later versions
Expand Down