Post reply

Transactional replication

  • February 3, 2010 at 1:09 pm

    #220255

    I wanted to know why should a table being published by transactional replication should have a primary key defined?

    what is the difference between how snapshot, merge and Transactional methods are implemented regarding the primary key.

    I tried getting the answer from BOL but it just mentioned that it needs to be defined but did not find any explanation for it.

    Can some one please let me know why?

  • February 3, 2010 at 2:05 pm

    #1113185

    PK is needed to identify which is row is being updated/inserted/deleted for Transactional and merge replication

    I assume you know what snapshot replication is and why it does not need PK

    -Roy

  • February 15, 2010 at 4:49 pm

    #1119017

    Roy Ernest (2/3/2010)

    PK is needed to identify which is row is being updated/inserted/deleted for Transactional and merge replication

    I assume you know what snapshot replication is and why it does not need PK

    I thought merge rep used the GUID system and triggers and not the PK to follow changes?

  • February 15, 2010 at 9:38 pm

    #1119058

    You are correct - merge replication uses the Row Guid Column to identify each record.

Viewing 4 posts - 1 through 3 (of 3 total)

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