Re: non logged transactions with transactional replication
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Sat, 11 Feb 2006 06:27:03 -0500
It doesn't handle not logged activity because it is based on logged events
and you can't do non-logged events on tables you are replicating.
Non-logged activity will occur when the bulk copy recovery model is selected
and
1) you do certain operations, i.e. create index, select into, etc
2) fast bcp - which requires no indexes on the table among other things
transactional replication requires a table with an index, so you can't do
fast bcp with it. It also requires publications built on preexisting tables
so you won't be able to replicate a table you are selecting into.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:59BAC0A1-DE3B-4E1B-A121-0C4E9B78497C@xxxxxxxxxxxxxxxx
I know that if you're doing log shipping and someone runs a fast bcp ( non
logged ) activity against the database that subsequent transaction log
dumps
won't load until you do another full dump and load. This can be a problem,
because of the time involved in dumping and loading. How does
transactional
replication handle non logged activity? The same way as log shipping?
Which
would be bad, or does the data that was inserted or changed as a result of
the non logged transaction make it to the target server?
.
- Follow-Ups:
- Re: non logged transactions with transactional replication
- From: Michael Hotek
- Re: non logged transactions with transactional replication
- Prev by Date: Re: Log Reader Agent remains after removing replication
- Next by Date: Re: Log Reader Agent remains after removing replication
- Previous by thread: Re: non logged transactions with transactional replication
- Next by thread: Re: non logged transactions with transactional replication
- Index(es):
Relevant Pages
|
