none
Alternative to SQL Server Replication

    Question

  • Hi Team,

    In the current architecture we have Microsoft dynamics CRM 2011 on premise system. CRM 2011 database is on  MS SQL Server. In the current architecture 3 SQL server replication is done for 3 external application databases. Customer has expressed replication is taking long time.

    We are upgrading icrosoft dynamics CRM 2011 on premise system to Microsoft Dynamics 365 on premise system. Dynamics 365 database will be on  MS SQL Server 2016. In the proposed architecture, 3 replication should be done for 3 external application databases.

    Do we have any other alternatives to SQL Server Replication ?

    Regards

    VGR


    Tuesday, May 29, 2018 4:47 PM

All replies

  • What do you mean "replication is taking long time"?  Are you referring to latency?    What type of replication are you using?

    This is probably a better question for the Dynamics CRM forum.

    Tuesday, May 29, 2018 5:15 PM
  • I concur with Tom's question. Does the latency exist when you are generating the snapshot or distributing transactions. CRM databases tend to have a lot of tables. No matter what alternative you try, you will struggle with this. You might find that using SQL Server Always On Availability groups will allow you to create a read only databases on your remote servers which might be an alternative here.
    Tuesday, May 29, 2018 5:44 PM
    Moderator
  • Hi Cotter,

    Latency is while distributing transactions to external application databases. The external application databases will be using SQL Server 2008 R2 and Dynamics 365 on premise will be using SQL Server 2016.

    Will SQL Server replication work ?

    Will SQL Server Always On Availability groups work ?

    Are there any third party software that can be used for SQL Server Replication ?

    Can we use Microsoft Sync Framework ?

    Regards

     G.R.Venkatesh


    Wednesday, May 30, 2018 9:17 AM
  • Transactional replication may work, but you are complaining about latency. This could be due to the work load or bottlenecks on the subscriber. You will need to examine wait stats there to determine what the bottleneck is.

    Always on AGs will create a read only copy of your databases on the secondaries. This might work for you if you want to offload reporting. The databases will be mirrors of each other. There is no possibility to have a different version of the database on the secondaries.

    There are other options like GoldenGate or SSIS. However I think you will run into the same problems with the large numbers of tables.

    Sync Framework has the same problem - you will also need to roll your own change tracking mechanism or use the SQL Server Change Tracking features.

    Wednesday, May 30, 2018 2:54 PM
    Moderator