Latency determines the amount of time between when SQL Server commits the transactions against the production database and when SQL Server applies those same transactions to the Subscribers' copy of the data.
When possible, prompt users to enter security credentials at runtime.
If you must store credentials in a script file, you must secure the file to prevent unauthorized access.
Distribution Database screen - Typically the distribution database name is 'distribution' but location of the distribution database and transaction log should be corrected to the correct paths for the SQL Server.
Publishers Screen - If more than one publisher is needed, use the interface below.
The overall setup is not difficult, but there are a few tricky areas you should be aware of during the setup and configuration.
Let's outline setup process in a step by step manner to better understand what is needed in order to make an informed decision about Updatable Subscription Replication in SQL Server 2005.
SQL Server 2005 has introduced a new replication method called "Updateable Subscription Replication" which allows data modification at both the publisher and the subscriber(s).
An option is also available to queue the data from the subscriber so the subscriber does not have to be on the network all of the time.
Transactional replication is a popular method of maintaining an updated copy of a production database.
The term for the remote secondary servers is Subscribers; the term for the primary production server is Publisher.