You work as a database administrator at TestKing.com. TestKing.com has 12 separate
branch offices and a main office, each office is equipped with their own SQL Server 2008 computer.
A database table named TK-Sales is used to store point-of-sale transactions. Furthermore,
TK-Sales also hosts sales information from all 12 of the TestKing.com branch offices to
accommodate customer returns of products. Consequently the data should be refreshed
from the main office to all 12 branch offices every hour, on the hour. To this end you make
use of a trigger called Stats_Trigger to produce sales statistics based on customer sales and
buying patterns. Currently replication between the server in each of the 12 branch offices
and a middle server in the main office occurs in real time. You need to decide which type of
replication would be best in this scenario. You should also eliminate the replication of the
data that is produced by the trigger.
What steps should you take? (Each correct answer presents part of the solution. Choose TWO.)
A.
A. You should consider using multiple merge publications, one at every branch office and
one in the main office.
B.
You should consider using transactions log between all the servers in the TestKing.com
domain.
C.
You should consider using snapshot replication.
D.
You should consider using merge replication.
E.
You should consider setting the Stats_Trigger trigger on the server in each retail store to
use the NOT FOR REPLICATION option.
F.
You should consider setting the Stats_Trigger trigger on the server in each retail store to
use the FOR REPLICATION option.
Explanation:
In some cases, it is desirable for user activity in a replication topology to be treated differently from agent activity.The NOT FOR REPLICATION option allows you to specify that the following database objects are treated differently when a replication agent performs an operation:
* Foreign key constraints
The foreign key constraint is not enforced when a replication agent performs an insert, update, or delete operation.
* Check constraints
The check constraint is not enforced when a replication agent performs an insert, update, or delete operation.
* Identity columns
The identity column value is not incremented when a replication agent performs an insert operation.
* Triggers
The trigger is not executed when a replication agent performs an insert, update, or delete operation.