Specifying articles.

We are finally to the real reason we are using replication, to replicate the tables in our database. This is where we will select all of the tables that will be replicated. You’ll notice a lot of buttons, items, and checkboxes in here. The grid on the left contains a list of all tables in your database. IN the far left column, you will notice a combination of checkboxes and keys with an X through them. One of the requirements for replication is that a primary key or unique index must be created on every table that will be replicated. The key with an X through it designates those tables wich do not have a primary key/unique index and can not participate in replication. To select a table for replication, simply place a check in the box. On the right hand side is a set of options. The first set will filter the list on eth left. This can be very useful when working with long lists or when modifying an existing article. The buttons at the bottom enable a single point and click to select all tables to be published or ot deselect all tables. Because we are using transactional publishing, we have the option to replicate both tables and stored procedures.

Replicating stored procedures can be extremely powerful and functions differently based upon the type of replication. If snapshot replication is used, then the entire stored procedure is replicated to each subscriber. In this way, you can keep a set of stored procedures replicated within your environment. With tansactional replication, the execution of the stored procedure is replicated instead of the data that is modified. This is extremely useful in envronments where stored procedures make large numbers of changes to existing data. If all of the data modifications were replicated, a significant overhead on the network can occur. Instead transactional replication causes the stored procedure to be executed at each of the subscribers. The only data that is transmitted is the actual comand to execute the stored procedure. However, the data will stil end up in the same state as if all of the data changes were transmitted to each subscriber.

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