question

niall5098 avatar image
niall5098 asked

log backup size after transactionl replication setup

HI All, i have set up transactional replication for a database in a 3 node always on cluster using the steps outlined below:

https://techcommunity.microsoft.com/t5/SQL-Server-Support/Setting-up-Replication-on-a-database-that-is-part-of-an-AlwaysOn/ba-p/318171

as a result of this the transaction log backups are quite large. i have rescheduled the tlog backup job to run every 5 minutes to maintain the log file size itself. My issue is i don't understand why the db log file is so busy after the replication setup.

has anyone else had this issue? any details would be greatly appreciated .

replicationsql server 2012always-ontransactional-replication
1 comment
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

ThomasRushton avatar image ThomasRushton ♦♦ commented ·

What do you see when you run the following query?

SELECT name, recovery_model_desc, log_reuse_wait_desc FROM sys.databases

(filter for the databases you're concerned about)

In particular, that last column?

0 Likes 0 ·

0 Answers

·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.