You probably will not be using remote servers in SQL Server 2005 -SQL Server 2014 versions.

If you do happen to use "remote servers", the RPC setting enables a certain security feature. If it is turned off, when the second server (the one receiving the login attempt from the first server to which the client connected) tries to validate the remote login, it fails with error

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.”

2. The RPC OUT setting is very pertinent to linked servers on SQL Server 2005 -SQL Server 2014 versions.

Think about an RPC (Remote Procedure Call) as being a stored procedure being run remotely from Server 1 to linked Server 2 "myserver".

There are various syntaxes, the first using 4 part naming servername.databasename.schemaname.procedurename , the second here using EXECUTE(databasename.schemaname.procedurename ) AT servername convention.

We can test with a simple procedure sp_helpdb that lives in master database, and will list out the databases and some of their key properties.

EXEC [myserver].master.dbo.sp_helpdb

EXEC ('master.dbo.sp_helpdb') AT myserver

These kind of remote stored procedure calls will be blocked unless RPC OUT is set to True.

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

You can set it to True or False in the linked server's properties (a right click menu in from the Linked Server Name in SQL Server Management Studio) .

Or you can set it by calling the stored procedure to set the server options like this test: