none
Merge replication for CRM 2016. RRS feed

  • Question

  • Good afternoon. There is a remote site where you use CRM Server 2016 consisting of two CRM servers and SQL 2014, one database. On our site we want to place also our capacities consisting of two physical servers for CRM. Between the offices the data transmission channel 100 mb/s. I want to use the same database at two sites, but that would change in the database could make the staff at both ploshadka. Prompt whether it is possible to use in this configuration with CRM SQL Merge Replication of this base ? 2.Also, employees working with CRM in a remote office use their root domain and their subnet, and our employees in our office are in a subdomain and in another network but the same active Directory forest. Tell whether the configuration of Merge Replication in different domains of one wood and in different subnets is possible ? Thank you!

    Люди тратят здоровье, что бы заработать $, а затем тратят $, что бы вернуть здоровье!

    Tuesday, July 9, 2019 2:07 PM

Answers

  • Thank you! It is clear that CRM does not support simultaneous data changes during replication. And if you try to divide CRM into backend/frontend, that is, to install backend/frontend on our site and from the point of view of working with a web-application it will be faster, but writing to the database will still be izti in SQL in another office and this will not solve the problem of optimization and fault tolerance ? However, there is an option to separate the database for your CRM, but it will require an organizational issue and a long migration of all configurations, and also a question of licensing.

    Люди тратят здоровье, что бы заработать $, а затем тратят $, что бы вернуть здоровье!

    • Marked as answer by rеstless Thursday, July 11, 2019 9:31 AM
    Wednesday, July 10, 2019 9:58 AM

All replies

  • How many SQL Servers do you have? It sounds like 2 but could be 3. If you use merge replication it will add a guid column to every table you are replicating which will likely put you in an unsupported scenario with your vendor.

    You should use peer to peer replication (Enterprise Edition Only Feature) or bi-directional transactional replication. 

    Tuesday, July 9, 2019 2:10 PM
    Moderator
  • Now one SQL is used on the remote site. The whole problem boils down to what would speed up the process of working with CRM in our site as well as install another SQL here and replicate it with remote. As well as in the event of a fall of the data channel and after its recovery, all data would be synchronized. We could use AlwaysOn technology, but unfortunately then we won't be able to make any changes on our side, only on our side. And changes can and should be made from both sides.

    Люди тратят здоровье, что бы заработать $, а затем тратят $, что бы вернуть здоровье!

    Tuesday, July 9, 2019 2:18 PM
  • What you want is peer to peer or bi-directional transactional replication. These both allow for writes on both sides and will keep both databases synchronized but not tightly coupled which could be a problem. 

    Identity ranges will be difficult to manage  - but not impossible.

    Tuesday, July 9, 2019 2:22 PM
    Moderator
  • that is in these configurations SQL Enterprise edition is necessary ?

    Люди тратят здоровье, что бы заработать $, а затем тратят $, что бы вернуть здоровье!

    Tuesday, July 9, 2019 2:30 PM
  • we have only one database.

    Люди тратят здоровье, что бы заработать $, а затем тратят $, что бы вернуть здоровье!

    Tuesday, July 9, 2019 2:31 PM
  • I could not find on this forum topic with the section CRM and dynamics.Can the experts in dynamics something to tell about supported configurations replication database on the SQL ?

    Люди тратят здоровье, что бы заработать $, а затем тратят $, что бы вернуть здоровье!

    Tuesday, July 9, 2019 2:34 PM
  • Thank you! It is clear that CRM does not support simultaneous data changes during replication. And if you try to divide CRM into backend/frontend, that is, to install backend/frontend on our site and from the point of view of working with a web-application it will be faster, but writing to the database will still be izti in SQL in another office and this will not solve the problem of optimization and fault tolerance ? However, there is an option to separate the database for your CRM, but it will require an organizational issue and a long migration of all configurations, and also a question of licensing.

    Люди тратят здоровье, что бы заработать $, а затем тратят $, что бы вернуть здоровье!

    • Marked as answer by rеstless Thursday, July 11, 2019 9:31 AM
    Wednesday, July 10, 2019 9:58 AM
  • Hi restless,

     

    Thank you for you reply. Have you solved this problem ?  In order to close this thread, please kindly mark useful replies as answers. By doing so, it will benefit all community members who are having this similar issue.  Your contribution is highly appreciated.

     

    Best regards,

    Dedmon Dai


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Thursday, July 11, 2019 5:36 AM