|
|
|
|
|
Replication Primer 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 These infinite loops are very easy to start in bi-directional replication. It is because of this situation that database participating in bi-directional replication usually contain a column indicating ownership of a piece of data. The publications are all custom configured so as to only replicate the set of rows that originated on a particular server.Since merge replication offers the same end result as bi-directional replication, it is highly recommended that you utilize merge replication instead of bi-directional replication.
Bi-directional replication Replicating in Mixed Environments Before getting to the heart of replication, it should be noted that SQL Server does support replication to non-SQL Server databases. It also supports replication between 6.5 and 7.0 databases. A SQL Server 6.5 system can use a distribution database residing on a 7.0 server. Since both versions of SQL Server can not be running at the same time, these need to be separate servers. The topology you would use for something like this would be a central publisher with remote distributor or publishing subscriber. SQL Server 7.0 supports push subscriptions to 6.x servers. This means that it can send data to the 6.5 server. It does not support pull subscriptions. You can also publish data to an ODBC datasource. There are five requirements for publishing to an ODBC datasource:
Replication Primer 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 |
All content on this site, except where noted, represents an original work of Michael R. Hotek and is protected by applicable copyright laws. The SQL Server FAQ is the sole work of Neil Pike. No page, portion of a page, or download may be used for commercial purposes in whole or in part without the express, written permission of the applicable author.
