Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In transactional replication - first 8000 rows of snapshot copies to subscriber snapshot then acts like it completed successfully.

Publication table has 21 million rows. Snapshot says completed successfully then we get the error "cannot find row at the subscriber" when transaction replication begins.

This is on a new 64 bit server running SQL Server 2005 Standard 64 bit SP3 with Cumulative Update 4. We have a standalone distributor also.

We upgraded the server / OS to Windows 2008 R2 64 bit and SQL Server from 32 to 64bit with the Cumulative Update 4 to take care of the paging issue/bug.

Has anyone ever ran into this situation?

share|improve this question

Could any operations be altering the values of the primary key columns of the table?

That error can be generated when a replicated update or delete statement cannot find a specific PK value.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.