Does doing a transaction log backup with 'Remove inactive entries from
transaction log' option selected and shrinking database to free up space
affect replication in anyway?
Thanks
GavGav,
merge is monitored using triggers so this isn't affected. Transactional will
remove only those commands read by the log reader agent (log is marked using
sp_repldone), otherwise it'll not truncate those commands. It might be that
the log reader agent will function faster having less records to filter by -
I have no way of knowing this without knowing the structure of the
transaction log and the query used. Certainly empirically I haven't noticed
a significant difference.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||Gav wrote:
> Does doing a transaction log backup with 'Remove inactive entries from
> transaction log' option selected and shrinking database to free up space
> affect replication in anyway?
> Thanks
> Gav
>
No, but the converse is true. Transactions cannot be flushed from the
log if they are waiting to be replicated, i.e. read by the LogReader agent.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thanks for the fast reply
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45A508CA.8060104@.realsqlguy.com...
> Gav wrote:
> No, but the converse is true. Transactions cannot be flushed from the log
> if they are waiting to be replicated, i.e. read by the LogReader agent.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Monday, March 19, 2012
Backup Database remove inactive/replication
Labels:
backup,
database,
entries,
fromtransaction,
inactive,
log,
microsoft,
mysql,
oracle,
replication,
selected,
server,
shrinking,
sql,
transaction
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment