Term
|
Definition
| can be used to automatically send articles to multiple subscribers. |
|
|
Term
|
Definition
| defines the most granular level of data distribution. |
|
|
Term
|
Definition
| the most granular level within the replication architecture. Publications are groupings of articles. |
|
|
Term
|
Definition
| can be applied to articles to restrict the set of data that is replicated. |
|
|
Term
| what are the three methods of replication? |
|
Definition
| snapshot, transactional, and merge |
|
|
Term
| what are the five agents used in replication? |
|
Definition
1. Snapshot Agent
2. Log Reader Agent
3. Distribution Agent
4. Merge Agent
5. Queue Reader Agent |
|
|
Term
|
Definition
this agent is responsible for extracting the schema and data that need to sent from publisher to subscriber
Used in Snapshot Transactional and Merge |
|
|
Term
|
Definition
It is used to extract committed transactions from the transaction log on the publisher that need to be replicated. It also makes sure that everything is written to the distribution database in exactly the same sequence as the transaction was issued.
ONLY USED IN TRANSACTIONAL REPLICATION |
|
|
Term
|
Definition
applies snapshots and sends transactions.
Used with snapshot and transactional replication |
|
|
Term
|
Definition
| Only used with merge replication. Applies snapshot when the subscriber is initialized and is responsible for exchanging transactions between publisher and subscriber |
|
|
Term
|
Definition
| Is used only when the queued updating option for transactional or snapshot replication has been enabled. It transfers the queue from the sub to the pub. |
|
|
Term
| What are the three types of data conflicts? |
|
Definition
1. Insert of a duplicate primary key
2. Update conflict
3. update of a nonexistant row |
|
|
Term
| what are the two roles that a database can have within a replication architecture? |
|
Definition
|
|
Term
| what are the core components of replication? |
|
Definition
| One or more articles that are combined into a publication (optionally with filter applied) |
|
|
Term
| Immediate Update Subscriber |
|
Definition
| allows changes to be made to the subscriber that are sent back up to the publisher |
|
|
Term
|
Definition
| Allows changes to be made on the subscriber and then sent back to the publisher. It periodically transfers the queue back to the publisher and then makes all the changes |
|
|
Term
| difference between queued update subscriber and immediate update subscriber? |
|
Definition
| Queued Update can cause data conflicts but can work is the publisher is not available. Once the publisher it sends it the transactions. In immediate update if the publisher is not available the transaction fails |
|
|
Term
| in transactional replication, if you could be processing changes that might generate data conflict, you cannot implement either a _________ or _________ architecture |
|
Definition
| bidirectional or peer-to-peer architecture. |
|
|
Term
|
Definition
tables are replicated across multiple databases.
Made up of several databases, each with its own distributer. No data conflicts can occur. |
|
|
Term
| bidirectional publication |
|
Definition
| two subscriber/publishers are using one distributer to share data. Different from peer-to-peer because only on distributer is necessary. |
|
|
Term
| name two options for performing transactional replication? |
|
Definition
| immediate update and queued update |
|
|
Term
| name two architectures for performing transactional validation |
|
Definition
| peer-to-peer and bidirectional |
|
|
Term
| what are two procedures that are used to validate whether a publisher and subscriber are synchronized? |
|
Definition
| sp_publication validation and sp_article validation |
|
|
Term
| which two tables allow merge replication to determine the changes that need to be synchronized between publisher and subscriber? |
|
Definition
| MSmerge_contents and MSmerge_genhistory |
|
|
