Post reply

Replication issue, specific column

  • October 17, 2016 at 1:48 pm

    #314519

    Hey all--

    Does anyone know of any exceptions for table replication?

    We have a large inventory table that we use - around 4 million parts - that is maintained on one server and then replicated to another via SQL Replication. For some reason, there is one particular column - part status - that is different on around 1400 parts. This seems to be the only column that is different between the two tables.

    As an aside, my theory is that some process is updating the table on the target side, but the developers don't seem to think so, so I am trying to cover all bases 😀

  • October 18, 2016 at 3:12 pm

    #1907277

    cphite (10/17/2016)

    Hey all--

    Does anyone know of any exceptions for table replication?

    We have a large inventory table that we use - around 4 million parts - that is maintained on one server and then replicated to another via SQL Replication. For some reason, there is one particular column - part status - that is different on around 1400 parts. This seems to be the only column that is different between the two tables.

    As an aside, my theory is that some process is updating the table on the target side, but the developers don't seem to think so, so I am trying to cover all bases 😀

    Never mind :b

    Turns out one of the devs submitted an update to our production team, and they ran it against the target side server instead of the source side.

Viewing 2 posts - 1 through 1 (of 1 total)

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