Memroy pressure caused by SQL Server publish Subscription (Replication) (Cmemthread wait)

Learn more about the next release subscription:

data replication : Allows a data source to distribute data to one or more target databases, accessible only to OLE DB providers;

the entire replication framework contains : Replication components, replication agents, replication types;

Replication components:

Publisher: The publisher uses data to replicate to other database servers that are available, tracks changes to data, and maintains other source database information;

Distributor: A server that distributes replicated databases, stores distribution databases, metadata, historical data (transactional replication) transactions;

Subscribers: is the target server for replication, replication database receive and update, subscribers can also change data (merge replication), you can publish data to multiple subscribers;

Project is the basic unit of replication

The project contains:

A complete table, some columns of a table, some rows of a table, a subset of tables, views, indexed views, user-defined functions, stored procedures;

Also contains whether to copy schema objects: Schema objects contain constraints, indexes, triggers, collations, extended properties,

Cannot contain system database (MASTER,MODEL,MSDB,TEMPDB)

Replication agent:

The Snapshot Agent (Snapshot.exe) creates a database snapshot that contains the schema and data, which is provided for the distribution database and is responsible for distributing the update state information for the database; Each publisher has a Snapshot Agent that connects to the distributor and is suitable for each type of replication;

The Distribution Agent (Distrib.exe) sends the database from the snapshot replication or the thing from the transactional replication to the Subscriber if the agent runs to the distributor, is a push subscription, and the agent runs to the subscriber, which is used for pull subscriptions, except of course the Merge Agent;

Merge replication (Replmerg.exe) runs to the publication and subscriber, and when a conflict occurs when synchronizing data updates, the rules set by the resolver are used to resolve the merge replication only;

The log Agent reads (Logread.exe) from the Publisher at the transaction log to move the tag copied things to the Distributor, +

Memroy pressure caused by SQL Server publish Subscription (Replication) (Cmemthread wait)