Hello, I have multiple databases using merge replication with , @publication_compatibility_level = N'90RTM', @replicate_ddl = 1. I have a backup job on the publisher database that does a full backup nightly. I have another job that backs up the transaction log every 3 hours and runs DBCC SHRINKFILE (N'TheDatabaseName_Log' ) on the publisher. I added a new subscriber to the replication environment but I did not get a chance to add any maintenance jobs to it yet(it is not 'live' yet). I noticed that even though I have data replicating to all the subscribing databases on the new subscriber the transaction log on the new ubscriber is not growing out of control and the recovery model is FULL. Can anyone tell me why the transaction log on the new subscriber does not "grow"? I don't recall this type of behavior for SQL 2000. Thanks.