May 30, 2012 at 12:59 pm
I know it depends on many factors.
We have transactional replication setup. I would like to know what's the min latency we can expect.
Thanks,
May 30, 2012 at 2:09 pm
deep_kkumar (5/30/2012)
I know it depends on many factors.
It does depend on a lot of factors. So many that it is not worth trying to answer your question. This is not to mention that those factors are variable.
We have transactional replication setup. I would like to know what's the min latency we can expect.
It sounds like you are considering splitting your reads and writes and you want to know what to expect if you write a row to the publisher and immediately try to read the row from the subscriber within the same application. If this is the plan then I would urge you to build provisions for the case when the row does not appear on the subscriber into your application otherwise you will always be chasing the issue. Replication is great for standing up a read-only reporting database where the subscriber can safely be a few seconds, or even minutes, behind the publisher. In cases where I have seen companies try to use it to scale out an application where the subscriber has to stay in perfect unison with the publisher it has not gone well. The better path is to scale up your server, tighten up your code, and maybe look into employing snapshot isolation or read committed snapshot isolation.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply