Home > IT Answers > SQL Server > Stopping transactional replication from skipping a block of records
SQL Server Ask the Experts
2,585 pts.
 Stopping transactional replication from skipping a block of records
SQL Server 2005, SQL Server snapshot backup, Transactional replication software
Have you ever run into an instance in SQL 2005 where transactional replication is skipping a specific block of records? I have tried many troubleshooting techniques: dropped/created sub and pub, created new empty destination table, reinitialized and several others. New transactions come across just fine. Do you have any advice on either completely resetting the snapshot to include these transactions or to simply move them over manually?

Software/Hardware used:
ASKED: June 18, 2008  7:31 PM
UPDATED: June 18, 2008  9:25 PM
RELATED QUESTIONS
Answer Wiki:
As long as you don't have any filters defined on the replication SQL shouldn't be picking which transactions to send across. Unless you have conflicts within a merge replication setup, you shouldn't have any problems. Are all updates not being sent across, only updates to records created before the replication was setup, etc?
Last Wiki Answer Submitted:  June 18, 2008  9:25 pm  by  Denny Cherry   64,520 pts.
All Answer Wiki Contributors:  Denny Cherry   64,520 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

Check out my SQL Server blog “SQL Server with Mr Denny” for more SQL Server information.

Denny Cherry
 64,520 pts.