certificates for cross db access without explicit user 
permissions to the dependent database or any tables therein


------------------------------------------------------------------
IN REMOTE DB (database with object to permission by certificates)

1. create a certificate
       
2. backup the certificate to files so we can create the same certificate in another database

3. create a user from the certificate (doesn't need to correspond to a login)

4. remove the private key from the certificate for added security (optional)

5. grant privs to this certificate user to the remote objects that you don't want regular users to access directly

------------------------------------------------------------------
IN LOCAL DB (database where the regular user will be calling SPs and functions)

6. create a certificate from the file backups in step 2

7. delete the files for security and general clean up reasons (optional)

8. "sign" [add signature] the SP/Function that needs permission to remote tables from the certificate

9. remove the private key of the signature for added security (optional)
------------------------------------------------------------------

Assuming the local user has permission to exec the local procedure they can now execute it
even though they don't have permissions themselves to the dependent remote tables or even
have access to the remote database.