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 |
|
T-Bone
Starting Member
8 Posts |
Posted - 2004-07-16 : 15:17:34
|
| For the second time in a week all of my replicated data at the subscriber has been deleted and then the distribution agent fails because "The row was not found at the Subscriber when applying the replicated command. Error number: 20598". This is transactional replication using SQL Server 2000 running on W2K.When this happened last week I deleted replication, recreated it, and everything ran fine until today. Everything else on the server is running fine, including other replication publications. Has anyone encountered a similar problem where all of the data on the subscriber gets deleted and then replication fails? If so, what can be done to prevent it from happening.Thanks in advance. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-07-16 : 18:49:38
|
| Do you trust everyone who has access to the database? Someone is deleting the data at the subscriber. The subscriber should not be touched in transactional replication.Tara |
 |
|
|
T-Bone
Starting Member
8 Posts |
Posted - 2004-07-19 : 11:16:38
|
| I agree that data is getting deleted but the users only have read access. Replication is the only process that is editing the records. That is why I'm trying to figure out how the records are getting deleting. (I still haven't figured it out.) |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-07-19 : 12:25:51
|
| Run SQL Profiler to find out who is doing what.Tara |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-08-10 : 01:23:38
|
| I also encountered the same problem. Since we are on a 24x7 operations, programmers usually become so tired at the end of their shift that they confuse one server to another.If you haven't found out who is doing the deletions, better issue a deny delete,update,insert on the replicated tables on the subscriber. |
 |
|
|
|
|
|