Working with SQL Servers' transactional replication I am having a
problem with the subscribers log growing to the size of the full
database that I am replicating. Currently I have a 53 gig database
that I have setup as my publisher. My distributor is on another server
with the subscriber. I am also using the "sync with backup" DB option.
I have log jobs running every five minutes on the publisher and the
distributor.
My snapshot agent is setup with the following profile option:
BCPBatchSize = 100000, HistoryVerboserLevel = 2, LoginTimeout = 15,
MaxBCPThreads = 30, QueryTimeout = 300.
My Distribution Agent has the following profile options: BCPBatchSize
= 100000, CommitBatchSize = 100, CommitBatchThreshold = 1000,
HistoryVerboseLevel = 1, KeepAliveMessage Interval = 300, LoginTimeout
= 15, MaxBCPThreads = 30, MaxDeliveredTransactions = 0, QueryTimeout =
300, TransactionsPerHistory = 100
Lastly I have the recovery model for the subscriber database set to
Simple.
As the snapshot is delivered to the subscriber the log file grows to
the same size as the database. Is this normal? I would think that
since I am BCPing the data into the database that the log would stay
at a manageable size. Does anyone have a suggestion?
Thank you in advance for any suggestions submitted.
