Re: non logged transactions with transactional replication

But, if you run a transaction that is truly minimally logged (BCP in
bulk-logged recovery model), you will have to reinitialize.

I don't understand why that is considered "bad". A minimally logged
transaction does not write everything to the tran log. Therefore, if you
were allowed to backup the tran log and restore it, you would wind up with a
corrupted database. With respect to replication, a minimally logged
transaction doesn't even hit the replication engine, so your publisher and
subscriber will completely out of synch and since there is no track of the
data, there is no ability to resynch them except by reinitializing.
(Replication doesn't even detect that a minimally logged transaction
occured.)

This is not an issue for either replication or log shipping. It is a side
effect of the way the transaction was executed. The replication and log
shipping features are simply protecting the integrity of the databases
against something they can not control.

--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.


"Paul Ibison" <Paul.Ibison@xxxxxxxxxxxxx> wrote in message
news:OMFC2BDLGHA.648@xxxxxxxxxxxxxxxxxxxxxxx
John,
it is my understanding that in the full recovery model, every change to
the database is logged, so there's no issue with transactional
replication. In SQL Server 2005 the transaction log may be backed up after
minimally logged operations (eg Bulk load operations in the bulk-logged
model) so log shipping is also possible.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)



.

Relevant Pages

  • Re: Replication bandwidth comparison
    ... Some workloads are insert heavy. ... Looks pretty update heavy to me! ... Looking for a SQL Server replication book? ... So an update transaction affecting 100 rows would be ...
    (microsoft.public.sqlserver.replication)
  • Re: MSRepl_Commands question
    ... make all database changes to the ... publisher and the subscriber and then reinitialize replication. ... We considered checking the status of the distribution agent but realized ... by checking their transaction number against this value. ...
    (microsoft.public.sqlserver.replication)
  • Re: Merge & Transaction Replication Question
    ... Director of Text Mining and Database Strategy ... Looking for a SQL Server replication book? ... different 'reporting' SQL 2000 server and use Transaction Replication ...
    (microsoft.public.sqlserver.replication)
  • Re: Distributed transactions, replication, views
    ... If you have significant processors on your server you can partition the ... The way replication works is that if a transaction is committed on the ... Looking for a SQL Server replication book? ... I have been tasked with restructuring a database. ...
    (microsoft.public.sqlserver.replication)
  • Re: Merge vs. Transactional
    ... The decision on when to use transactional replication over merge replication ... lose the transaction. ... consistency between the publisher and subscriber. ...
    (microsoft.public.sqlserver.replication)