locked
SQL 2014 AlwaysOn to SQL 2017 AlwaysOn RRS feed

  • Question

  • Is there a way to easily migrate a SQL 2014 AlwaysOn cluster to a SQL 2017 AlwaysOn cluster?

    Can we connect the two clusters and replicate the databases in order to migrate them from 2014 to 2017?

    Thanks,

    Jay

    Monday, December 17, 2018 5:16 PM

All replies

  • Hello Jay,

    Check this forum post which is similar to your question.

    In addition to above, you can try below too,

    You can setup Logshipping from 2014 to 2017. You can disable logshipping during production cutoff and make the databases online in SQL Server 2017. But for this to work, SQL Server 2017 database which is your logshipping destination should not be part of Alwayson.

    Setup replication from 2014 to 2017. This will allow your SQL Server 2017 databases to be part of Alwayson. But latency issues can be cause of concern. Databases of huge size can be challenging.

    Regards;
    Vivek Janakiraman

    Tuesday, December 18, 2018 12:25 AM
  • Hi Jay,

    Do you mean Always On failover cluster or Always On availability group?

    If you are using Always On failover cluster, you can easily do this like migrating databases from one instance to another. But for Always On availability groups, you will need to add these databases back the new AG. Please refer to the document from Migrating database from AlwaysOn AG to another with JoinOnly option.

    Since you are planning to upgrade to a modern data platform, the Data Migration Assistant (DMA) can be used to detect compatibility issues and move data to your new version of SQL Server. And for large migrations, it is recommended to use the Azure Database Migration Service, which can migrate databases at scale. For more information, please refer to Overview of Data Migration Assistant.

    Best Regards
    Puzzle
    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

    Tuesday, December 18, 2018 6:01 AM