Is this an expected behaviour or known issue regarding proxy tables?
I created a proxy table in server SRV_S that points to a table in SRV_P. I then created a procedure in SRV_S that selects data from proxy table, however the procedure is failing with select permission error
Msg 10330, Level 14, State 1:
Server 'SRV_S', Procedure 'usp_GetAccounts', Line 4:
SELECT permission denied on object Accounts, database CLM, owner dbo
Command has been aborted.
The user exists on both servers. I tried executing the procedure with a user that has sa_role on both servers and the execution of the procedure was successful (because that user would have had full access to the DB and table)
Why would you need select permission on a proxy table to execute a stored procedure that references that table?