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 |
|
sona
Yak Posting Veteran
68 Posts |
 Posted - 2004-01-28 : 07:17:12
|
| I have transactional Replication from A to B.My distribution agent failed becos of a primary key violation error in a table.[i have no included the skipp error option].Then the replication stopped.The transactions on other tables are also not replicated to B.IF an error is encountered in one of the tables will the replication stop entirely.Is there no way for the replication to continue for the rest of the tables..Pls clarify |
|
|
VyasKN
SQL Server MVP & SQLTeam MVY
313 Posts |
Posted - 2004-01-28 : 10:31:11
|
| What you are seeing is the expected behavior. If there's a problem with one table, then, none of the other tables replicated by the same distribution agent will receive any changes.One way to get around it is to create different smaller publications with few tables per each publication, and then specifying 'independent agent' property of the publication to true.--HTH,Vyashttp://vyaskn.tripod.com |
 |
|
|
|
|
|
Replication problem