InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 22 May 2013 11:49:25 GMT20http://www.sqlservercentral.com/Forums/Topic1428720-359-1.aspxIt depends on how the Linked Server is configured. If you have the certificate working then it should be a trivial thing to test using a Linked Server from inside a certificate-signed stored procedure. If you run into errors, post your Linked Server definition and the error message.Sun, 10 Mar 2013 18:53:21 GMTopc.threehttp://www.sqlservercentral.com/Forums/Topic1428720-359-1.aspxThanks I got it working using certificate. Question though...How about linked server? If I have the proc loads records in a table in different server?Sun, 10 Mar 2013 12:56:23 GMTSQL_Surferhttp://www.sqlservercentral.com/Forums/Topic1428720-359-1.aspxSchemas do not own things, but I know what you mean.In that case you can look into certificate signing or EXECUTE AS. I would go for certificate signing, it's a bit cleaner and you do not need to deal with impersonation.Fri, 08 Mar 2013 13:35:37 GMTopc.threehttp://www.sqlservercentral.com/Forums/Topic1428720-359-1.aspxBut he second db's table where the insert is going to take palce is owned by different schema.Fri, 08 Mar 2013 13:31:47 GMTSQL_Surferhttp://www.sqlservercentral.com/Forums/Topic1428720-359-1.aspx[quote][b]SQL_Surfer (3/8/2013)[/b][hr]I have a stored proc that gets executed by SQL login which has execute access to the schema owned by stored proc.Inside the stored proc, it has insert statement to another DB which this sql login doesn't have access to. How do I get around it?Third party app calls the stored proc.Thanks for your help.[/quote]This constitutes a broken ownership chain. You can look into cross-database ownership chaining and the use of EXECUTE AS. You can also explore signing the procedure with a certificate that has access to all underlying resources.Fri, 08 Mar 2013 12:48:38 GMTopc.threehttp://www.sqlservercentral.com/Forums/Topic1428720-359-1.aspxI have a stored proc that gets executed by SQL login which has execute access to the schema owned by stored proc.Inside the stored proc, it has insert statement to another DB which this sql login doesn't have access to. How do I get around it?Third party app calls the stored proc.Thanks for your help.Fri, 08 Mar 2013 11:49:14 GMTSQL_Surfer