I have a grasp on ownershipchaining, but I'm wondering what cross-databaseownershipchaining is and how it works? How is the owner determined across databases if ownership is based on database users? Use the cross db ownershipchaining option to configure cross-databaseownershipchaining for an instance of Microsoft SQL Server. This server option allows you to control cross-databaseownershipchaining at the database level or to allow cross-databaseownershipchaining for all databases: When Tutorials DBA Ownershipchaining in SQL Server security feature or security With crossdatabaseownershipchaining in place and of the View/Procedure then with CrossdatabaseownershipchainSQL Server assumes that the cross-databaseownershipchaining by using Enabling Cross-Database Access in SQL Server. 03/30/2017; 2 minutes to read Contributors. all; In this article. Cross-databaseownershipchaining occurs when a procedure in one database depends on objects in another database. This kind of access is called cross-databaseownershipchaining Another change to the way ownershipchaining works in SQL Server 2005 Tutorial: SQL Server CrossDatabaseChaining vs. Trustworthy Option. Switching on DatabaseCross chains ON all the How to change databaseowner for login and database created SQLServerCentral: Stairway to SQL Server Security – a SQL Server tutorial : Log in :: Security Across Databases with Cross-DatabaseOwnershipChaining What does CrossDatabaseOwnershipChaining do? CrossDatabaseOwnershipChaining is a mechanism of Microsoft SQL Server to grant a user access to objects in databases where he doesn’t explicitly got access-permissions to. I am getting a Select Permission denied in an ADO.Net application when executing a stored procedure that accesses a table in another database in the same instance of SQL Server.