Filtered Replication allows you to choose the documents that would
be replicated. Replicating only a selected part of your database
can be useful in numerous cases, e.g. -
To keep documents confidentiality
When an organization whose main database serves multiple departments,
facilities or branches use Filtered Replication to keep documents
The central database of a healthcare network, for example, can protect
patients' privacy by updating each clinic's database instance only with
records of patients treated by this clinic.
As an additional security measure
A central database that an array of traffic enforcement cameras replicate
speed tickets to, for example, can use Filtered Replication to restrict
each camera's replication to just tickets generated by this camera.
This will prevent a potential hacker from replicating a stolen camera's
speed tickets as if they were collected by another camera (e.g. to overrun
a ticket collected by any chosen camera, with a blank one).
To access the Hub or Sink Task Studio interface:
a. Open the Databases view in the source server.
b. Select the database where the task will be active.
c. Click Tasks tab.
d. Select Ongoing Tasks
e. Click Add a database task
f. Click Replication Hub or Replication Sink.
g. Toggle desired configurations and click Add Access to view the following interface:
Select existing access or define a new sink/hub, then click Save to create a new replication access where filtration is defined.
- Both the Hub and the Sink can filter data
Only documents matching the filters defined by both will be replicated.
- Documents are selected by path
Paths can include wildcards (
exact document IDs (
- Read and Write filtering
You can further increase filtering resolution, by
defining separate lists of allowed paths for incoming
and outgoing documents.