Missing records on Subscriber - Validate Subscription?

  • I have a fairly basic replication model set up, with a single Publisher and a single Subscriber. No filtering takes place on any published articles.

    Some records in a particular table don't exist on the Subscriber.

    Other related tables are there in their entirety, but then again some related tables are not.

    It's something I'll need to investigate as to how this started (I know some data was imported into the mentioned tables at the Publisher) but the immediate concern is how to synchronise the tables again, ideally without sending an entire snapshot to the Subscriber.

    Would Validate Subscription do something along these lines?

  • Validating a subscription will only notify if there are problems but it will not fix anything.

    (I'm still new at this so someone should probably confirm).

    You might want to check your conflict tables to make sure that your missing rows are not there.

  • 1 st u check repl momitor.there is any row filtering

  • Thanks. There is no row filtering or column filtering, and although there are some conflicts none of these match the records that are missing.

    I have done some digging and have found a utility that fixes the issues (in theory) but I have some new questions about this, so will start it in a new thread.

  • Was following along - what is the new thread how did you resolve looking for the same answer too.

  • Adrian Robertson (8/6/2008)


    Thanks. There is no row filtering or column filtering, and although there are some conflicts none of these match the records that are missing.

    I have done some digging and have found a utility that fixes the issues (in theory) but I have some new questions about this, so will start it in a new thread.

    validatesubscription does just that "valiadate" meaning it shows you if it is valid/invalid.

    Are you talking about Merge or Transactional replication ?


    * Noel

  • transacational.

  • There are several cases (BUGS) which could make that problem happen and some of them are documented in the MS KB.

    EX:

    http://support.microsoft.com/kb/954054/en-us

    http://support.microsoft.com/kb/951120/en-us

    There is also the possibility that someone/something changed the data on the replica but that's for you to find out.


    * Noel

  • Thanks i will review

  • i did have a look at the threads

    Our version is

    Microsoft SQL Server 2005 - 9.00.3228.00 (X64) Feb 9 2008 09:33:32 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)

    Cumulative update package 9 how do i know which accumulative patch i got

    I cannot see MaxCmdsInTran either in the log reader settings ...

  • how do i know which accumulative patch i got

    http://support.microsoft.com/kb/937137


    * Noel

  • Thanks and for the updates on replication

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply