Groups | Blog | Home
all groups > sql server replication > april 2007 >

sql server replication : Regarding replication and select



Iter
4/29/2007 4:16:01 PM
Hi Guys,
I have question regarding replication. I have 30000 rows data that need to
replicate from server A to Server B. It might last 2 hours to finish it. My
question is that can I select from tables in server B that were replcated
from server A? I cannot put nolock in query statement. I am fraid that tables
in server B have been locked resulting I cannot select data. Can someone give
Paul Ibison
4/30/2007 12:50:00 AM
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,
Iter
4/30/2007 6:24:00 AM
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
5/1/2007 1:22:00 AM
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
AddThis Social Bookmark Button