Post reply

Transactional publication with updatable subscriptions on SQL2012 release.

  • December 5, 2013 at 2:30 pm

    #302107

    Hi,

    We have a 4 serves around the world that needs to be in updatable subscriptions.

    Server location & versions:

    2 servers in North America – SQL server 2012

    1 server in Europe – SQL server 2008 R2

    1 server in Singapore – SQL server 2008 R2

    I created Transactional publication with updatable subscriptions (2 articles ) on one of the North America sever 2012 (by script method) and adding remaining 3 server (2012 & 2008R2) has Subscribers. Most of the major load happens on North America sever 2012.

    I was able to do it good, it was working has I was thinking.

    There is Stored procedure (web application) using MERGE (Performs insert, update, or delete operations on a target table based on the results of a join with a source table) to load tables.

    When we try using MERGE the Queue Reader agent fails below is error message. (Without MERGE it works fine).

    Error Message:

    The Queue Reader Agent has encountered the error ''Cannot insert the value NULL into column ''msrepl_tran_version'', table ''DataBasename.dbo.conflict_TableName''; column does not allow nulls. INSERT fails.'' when conn

    My question:

    1.In Transactional publication with updatable subscriptions, Merge operation can’t be used?

    2.I am not sure , which is the best way to do Transactional publication with updatable subscriptions on SQL12 (by script method) or I can user Peer –to-Peer Replication?

    3.Any help error message.

    4.Where should be the conflict tables created. For my Publication conflict tables are on publication is it the right way?

    5.We need to use the MERGE because, it save lots of data and would save time for better performance.

    Any help is greatly appreciated.

    Thanks.

  • December 6, 2013 at 7:42 am

    #1671527

    From books online:

    The MERGE statement should not be used when using queued updating replication. The MERGE and queued updating trigger are not compatible. Replace the MERGE statement with an insert or an update statement.

  • December 6, 2013 at 8:04 am

    #1671538

    Thanks for your reply.

    when we run the MERGE on SQL server 2012 it runs fine.

    But when it runs on SQL server 2008R2, the queue reader agent fails with

    Error Message:

    The Queue Reader Agent has encountered the error ''Cannot insert the value NULL into column ''msrepl_tran_version'', table ''DataBasename.dbo.conflict_TableName''; column does not allow nulls. INSERT fails.'' when conn

  • December 6, 2013 at 9:32 am

    #1671580

    Merge statement is compatible with Peer to Peer replication?

  • December 9, 2013 at 8:50 am

    #1671996

    HELP Please..!

    Merge statement is compatible with Peer to Peer replication?

  • December 11, 2013 at 9:02 am

    #1672667

    any help please.

Viewing 6 posts - 1 through 5 (of 5 total)

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