We are trying to implement Replication on a SQL database that is connected to by one of our c# applications.
The application uses both a SQL database and another tool (Source Depot) to store some data.
Because of this, the information on the database and the depot need to be kept in sync, or the application breaks.
Typical changes to the db are the addition of a line to a table, and at the same time the client application will add a new version to a file to source control.
We are using transactional replication and writing to the publisher only, while using the subscribers for improving performance over the WAN.
Our latency for the replication of a transaction right now is about 3 seconds, but it will be worse if we were to roll this system out to other locations (we are only testing its feasibility now).
Because of the need to keep the SQL and SD in sync, we are getting errors when connecting to the db after a write operation was done on the publisher (so, a line was added to a table), because Source Depot will report the latest information,
but the SQL will take 3 seconds to replicate the new line.
Is there any way that we can fix this? Ideally the subscriber wouldn't report obsolete information, but wait until the new data had been replicated... does the Subscriber have any knowledge of
View Complete Post