December 8, 2011 at 9:31 pm
Experts,
We have few snapshot replication setups(SQL 2008) with below configuration setups,
•Publisher, distributor on the same SQL server – Remote access configuration enabled
•Subscriber on separate server – Remote access configuration enabled
•Push type subscription configured
Please advise remote access should be enabled on both publisher,subscriber for the remote connections to happen?
Appreciate if somebody pass me the reference for replication transactions internal architecture..
Thanks in advance.
December 9, 2011 at 2:02 am
Use the remote access option to control the execution of stored procedures from local or remote servers on which instances of Microsoft SQL Server are running. Set remote access to 1 (default) to grant permission to run local stored procedures from remote servers or remote stored procedures from the local server. Set the option to 0 to prevent local stored procedures from being run from a remote server or remote stored procedures from being run on the local server.
The remote access option only applies to servers added using sp_addserver and is included for backward compatibility.
The setting takes effect after the server is restarted.
Note
This feature will be removed in the next version of Microsoft SQL Server. Do not use this feature in new development work, and modify applications that currently use this feature as soon as possible. Use sp_addlinkedserver instead.
See Also
Reference
RECONFIGURE (Transact-SQL)
sp_configure (Transact-SQL)
Concepts
December 9, 2011 at 2:03 am
December 9, 2011 at 4:38 am
Thanks for the reference.
My main concern is that 'remote access' configuration is mandatory for applying replication transactions on the remote server?
We have security concern in enabling remote access configuration. Will replication continue to work after disabling 'remote acess'?
Does 'remote access' involve in anyone of the following?
1) Applying the initial snapshot to the subscriber database (all types of replication, Snapshot replication)
2)Logreader agent moving the transactions from publisher to the subscriber server.
3)Synchronising the transactions in the publisher database of updatable subscriptions setting
Thanks again.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply