grant read access on a view but not on it's underlying tables from other databases
<p>I want to grant read permissions for a user for a view which joins 2 tables from another database.
<strong>I don't</strong> want to: </p>

<ol>
<li>give him permission on the database where the tables are or add him as an user there.</li>
<li>Make him the owner of the view/schema due to the security exploits.</li>
<li>I don't want to create first a table, or variations of a hack table with a <code>truncate</code> and a stored procedure which inserts the data on a trigger.</li>
</ol>

<p>Can this be done somehow? Maybe there's something I missed and you guys might know.</p>

<p>I have read these posts but they didn't solve my problem:
<a href="https://stackoverflow.com/questions/4134740/grant-select-permission-on-a-view-but-not-on-underlying-objects">Grant SELECT permission on a view, but not on underlying objects</a></p>

<p><a href="https://stackoverflow.com/questions/368414/grant-select-on-a-view-not-base-table-when-base-table-is-in-a-different-database">Grant Select on a view not base table when base table is in a different database</a></p>

<p><a href="https://msdn.microsoft.com/en-us/library/ms188676.aspx" rel="nofollow noreferrer">https://msdn.microsoft.com/en-us/library/ms188676.aspx</a></p>

<p><a href="https://dba.stackexchange.com/questions/89632/sql-server-grant-select-access-to-a-user-in-a-view-and-not-in-its-tables">https://dba.stackexchange.com/questions/89632/sql-server-grant-select-access-to-a-user-in-a-view-and-not-in-its-tables</a></p>

<p>Thank you</p>

<p><strong>Edit:</strong>
The easiest solution I came up with, after some research, is activating the <code>cross database ownership chaining</code>option on the database where I'm placing the views and granting the read permission to the users. This might be in contrast with my 2nd point of things I'm trying to avoid. Is this a good idea?</p>