RTaylor2208 (11/29/2013)
What are you thinking is an issue?Is it the distribution DB is too big?, with the latency and undistributed commands details you have provided it appears your replication is running as expected.
Reducing your max rentention period will store less within your distribution db, but the longer you have available will mean that in the event the subscriber is down for a sustained period, as long as that period is smaller than the retention period the subscription will not expire.
Hi RTaylor2208,
Thank you for your reply.
You are correct, I don't see an immediate issue at this time but, I do see a continually growing commands and transactions table (However, I am continually monitoring and seeing the counts beginning to come down. Will try to see if there will be an average amount of records for transactions and commands in the meantime.). Yes, I understand that the subscriber will not expire under the given circumstance. I just wondered if there is an optimal way to configure the distributor properties other than accepting the standard default when replication is setup? You are correct in that, at this time I should leave things as is until I need to make a change. Is there an advice you can provide on configuration of such properties?