70-450 · Question #127
You administer a SQL Server 2008 instance. The instance is one of three servers in a peer-to-peer transactional replication topology. The publication contains a table named Orders. The Orders table…
The correct answer is C. Use the BULK INSERT command in multiple staging tables. According to the exam resources, the answer is A). But according to MSDN, partition switching is not supported when the source or destination table is involved in replication. The vagueness of the question doesn't help. If we assume latency refers to the time between data…
Question
You administer a SQL Server 2008 instance. The instance is one of three servers in a peer-to-peer transactional replication topology. The publication contains a table named Orders. The Orders table contains 200 GB of data across multiple partitions. A batch process bulk loads 10 GB of data to the Orders table periodically. You need to design a replication strategy to minimize latency. What should you do?
Options
- AConfigure the Distributor agent to replicate transactions continually.
- Bmay be the optimal solution. Using the -continuous option on the distributor will ensure that
- CUse the BULK INSERT command in multiple staging tables.
- DDisable the Distributor agent. Use the BULK INSERT command in the Orders table.
How the community answered
(67 responses)- A4% (3)
- B9% (6)
- C84% (56)
- D3% (2)
Explanation
According to the exam resources, the answer is A). But according to MSDN, partition switching is not supported when the source or destination table is involved in replication. The vagueness of the question doesn't help. If we assume latency refers to the time between data replication, then transactions are replicated as quickly as possible. The commit batch threshold refers to replication commands and isn't relevant here. Note: Answer confirmed on exam as A), regardless of whether this is actually correct or not.
Topics
Community Discussion
No community discussion yet for this question.