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 |
|
SimonGough
Starting Member
23 Posts |
 Posted - 2002-01-14 : 05:10:48
|
| Hi.I'm in the situation where I have to maintain a synchronous database over two sites. Any changes made to the database from either site has to be replicated to each server.Can anybody suggest a strategy for approaching this problem with regard to publishers, distributors and subscribers. At the moment I'm testing out SQL server by having one server (server A) act as a publisher/distributor and the other server (server B) acting as a subscriber. I'm also using transactional publications.I can get any changes I make on Server A to replicate to Server B but not the other way round.. Another problem that I have noticed is that table ID's numbers appear to be out of sync with each other. (Caused by errors etc.)Any help would greatly be appreciated,Thanks. |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-01-14 : 13:19:39
|
| It really depends on your time requirements. Replication cannot ensure Realtime.I would use either Merge, or Transactional with immediate updating subscribers. Again, depending on your requirements. Check BOL to determine which you should use.-Chad |
 |
|
|
SimonGough
Starting Member
23 Posts |
Posted - 2002-01-15 : 04:21:05
|
| We are using Transactional with immediate updating subscribers at the moment. What is BOL?The main problem is ensuring syncronisation of ID's over the two databases. Surely, differing ID's in the 2 db's would cause problems?Can anyone help?Thanks. |
|
|
|
|
|
|
SQL Replication Problems