Merge replication and snapshot replication do not affect transaction log size, but transactional replication can. If a database
includes one or more transactional publications, the log is not truncated until all transactions relevant to the publications have
been delivered to the distribution database. If the transaction log is growing too large, and the Log Reader Agent is running on
a scheduled basis, consider shortening the interval between runs. Or, set it to run in continuous mode. If it is set to run in
continuous mode (the default), ensure that it is running.
Submitted questions and answers are subject to review and editing, and may or may not be selected for posting, at the sole discretion of w3Sniff.
Get Started
Comments
Leave a Comment