Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-01-10 : 08:33:01
|
| writes "We are setting up replication from one server in San Diego to a server in the UK. We are using Onyx CRM Software. We are able to replicate tables from San Diego to UK however we need to have two way replication. We have tried transactionaly replication with immediate updating subscribers however this process adds a uniqueidentifier column."In SQL Server 2000, tables used in publications that allow immediate updating are required to have a SQL Server uniqueidentifier column. If one does not exist, SQL Server 2000 adds one automatically when you create the publication. If you stop publishing a table, you can drop the uniqueidentifier column. Applications will work unchanged against tables with the uniqueidentifier column because you do not have to include this column in qualified INSERT, UPDATE, or DELETE statements."This is causing the Onyx application to fail. Is there any work around to have two way replication without adding uniqueidentifier columns to all tables that we replicate." |
|
|
JamesH
Posting Yak Master
149 Posts |
Posted - 2003-01-14 : 16:13:38
|
| If you remove the Immediate update from the Transactional replication then it doesn't require the timestamp value. Over the wire you will find that immediate updating won't work as well. I replicate to and from China using Transactional but I schedule the distribution agent to fire off every minute, this way if it fails on the first, then it will usually work the next time. It has gained me some sleep.Hope this helps.JamesH. |
 |
|
|
|
|
|
Replication