Sdílet prostřednictvím


cross db ownership chaining Option

Use the cross db ownership chaining option to configure cross-database ownership chaining for an instance of Microsoft SQL Server.

This server option allows you to control cross-database ownership chaining at the database level or to allow cross-database ownership chaining for all databases:

  • When cross db ownership chaining is off (0) for the instance, cross-database ownership chaining is disabled for all databases.

  • When cross db ownership chaining is on (1) for the instance, cross-database ownership chaining is on for all databases.

  • You can set cross-database ownership chaining for individual databases using the SET clause of the ALTER DATABASE statement. If you are creating a new database, you can set the cross-database ownership chaining option for the new database using the CREATE DATABASE statement.

    Setting cross db ownership chaining to 1 is not recommended unless all of the databases hosted by the instance of SQL Server must participate in cross-database ownership chaining and you are aware of the security implications of this setting. For more information, see Ownership Chains.

Controlling Cross-Database Ownership Chaining

Before turning cross-database ownership chaining on or off, consider the following:

  • You must be a member of the sysadmin fixed server role to turn cross-database ownership chaining on or off.

  • Before turning off cross-database ownership chaining on a production server, fully test all applications, including third-party applications, to ensure that the changes do not affect application functionality.

  • You can change the cross db ownership chaining option while the server is running if you specify RECONFIGURE with sp_configure.

  • If you have databases that require cross-database ownership chaining, the recommended practice is to turn off the cross db ownership chaining option for the instance using sp_configure; then turn on cross-database ownership chaining for individual databases that require it using the ALTER DATABASE statement.