Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When setting up a linked server in SQL Server (we're on 2005), you can set two server options:

  • Rpc
  • Rpc Out

Looking at the MSDN article, all it states is:

RPC - Enables RPC from the specified server.

RPC Out - Enables RPC to the specified server.

My question is, why would I need to set these options? What can I do / not do by enabling Rpc on a linked server? Does setting these options to true have any drawbacks?

EDIT:

But to execute the remote stored procedure, you'd need the "RPC Out" setting enabled. When would you ever need the "RPC" setting enabled?

share|improve this question
up vote 7 down vote accepted

An example of an RPC in this context is a stored procedure. To link another server and run an sp on it you'll need to set the RPC Out option.

-Anders

share|improve this answer
    
Thanks for the answer. I understand now that you need RPC Out enabled to execute a stored procedure on the linked server. Why would you ever need RPC enabled though? Why would you go through a linked server to execute a local procedure? Or am I missing something? – Aaron Daniels Jun 24 '09 at 14:01
    
There are many times when you may want to execute a stored procedure on a remote server. If you needed to make a bunch of changes to a remote database as part of a load process, executing a remote stored procedure would be the best method. – mrdenny Jun 24 '09 at 15:31
    
But to execute the remote stored procedure, you'd need the "RPC Out" setting enabled. When would you ever need the "RPC" setting enabled? – Aaron Daniels Jun 24 '09 at 18:18
    
When the linked server is more like a partnership than a client/server relationship. – chankster Jun 25 '09 at 9:47

I know this is old, but I came across this information below. RPC really doesn't do anything. You just need RPC OUT enabled.

external link to the information I found

share|improve this answer

I know this is an old question but it returns as one of the first links on a search. I am just adding to @chankster answer to give a bit more detail and when to use it. I don't have enough rep. to post it as a comment yet. Same answer I gave on http://dba.stackexchange.com/a/107042/70662. According to a msdn blog the RPC vs RPC Out on a SQL Server linked-server is this:

  1. RPC - This setting is mainly for legacy feature called Remote Server. According to the blog it states you will not be using this in SQL Server 2005 and higher. Unless you get an error like:

18482 “Could not connect to server '%.*ls' because '%.*ls' is not defined as a remote server. Verify that you have specified the correct server name. %.*ls.”

  1. RPC Out - setting is very pertinent to linked servers on SQL Server 2005 and higher. If this is not enabled you can get the following error message:

Msg 7411, Level 16, State 1, Line 1 Server 'myLinkedServer' is not configured for RPC.

Which really should say RPC Out should be enabled.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.