|   | ![]() |
|
Replication Primer 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 Click the Next button to display Figure 14-38.
Determining a schedule The publication we are subscribing is transactional and resides on the same server. In this case, we want to have continuous replication since this will send the data as soon as possible. You can batch replication by selecting a schedule option. This can be very effective when delaing with slow WAN links, dial up connections, ISDN, or systems that connect at preset intervals. In the case of slow WAN links, you minimize the time frame when you place a load on the network. With ISDN, you can save a significant amount of money by batching replication. With this option, you normally pay a usage fee based upon a discrete unit of time. By scheduling replication to occur and preset intervals, you can maximize your use of that time. Select the Continuous option and click the Next button to display Figure 14-39.
Define the intial snapshot options. When beginning replication, you want to make sure data is in synch and has a place to go. There are two options in this screen that are used at different times and under very different situations. The Yes option will create all of the tables and populate them with data in a single step during synchronization. This an option you would normally select during the first time replication is set up. There is a checkbox that is associated with this option as well. Selecting this will immediately start up the Distribution process and transfer the schema and data as soon as you complete the subscription. The no option does not create any of the tables, nor does it synchronize any data. You may be asking why this is even here. The process of replicating data can not start until a synchronization has completed between the publisher and subscriber. This tells SQL Server that the data matches and it can begin applying transactions on the subscriber. You may have already created the tables and prepopulated them with data. In this instance, you do not want the synchronization process to redo the work you have just performed.
Replication Primer 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 |
All content on this site, except where noted, represents an original work of Michael R. Hotek and is protected by applicable copyright laws. The SQL Server FAQ is the sole work of Neil Pike. No page, portion of a page, or download may be used for commercial purposes in whole or in part without the express, written permission of the applicable author.