Willem Tilstra-440027 (3/4/2013)
Gail Shaw mentioned in another forum question while I was researching this, that 'Replication does not in any way use the Subscriber's log file'.
Whoever said that should be taken out and shot. Oh, wait... 😀
The replication agents don't in any way read from or directly write to the subscriber's log, the subscriber's log (unless it's republishing) is just a normal transaction log used for normal database logging
I'm not sure that I understand the seeming contradiction been the updating going on in the Subscriber database, Full Recovery mode, no Transaction Log backups taking place and the Transaction Log not filling up.
Have you ever taken a full backup of the subscriber? If not, then the DB is in pseudo-simple recovery and the log is automatically being reused. It'll stay that way until someone takes a full backup.
Have you got any process (manual or automatic) switching the DB to simple recovery and back to full? If so, the DB is in pseudo-simple recovery until a full backup is taken.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability