taHy Paul,
I use sql 2000. What you mean is that it will block client application to
select if I use
default CommitBatchThreshold. What does it mean for CommitBatchThreshold? Is
that mean after each CommitBatchThreshold, the reolication commit the
transaction? If it is like this, so the client application can select from
replication table, right? Thanks.
[quoted text, click to view] "Paul Ibison" wrote:
> If you are on SQL Server 2005 you could use Read Snapshot Committed isolation
> level. Alternatively if you are referring to transactional replication and
> the commands have been replicated in a transaction, you could use
> -CommitBatchThreshold 1. Must admit that this is untested by myself, and
> could lead to breaking the acid properties of a transaction if you ever get
> an error.
> Cheers,
My understanding of setting the CommitBatchThreshold to 1 is that it'll chop
up your larger transactions into a series of 1 command transactions. This
breaks ACID properties, but increases concurrency.
Rgds,
Paul Ibison