Blog Post

Azure SQL Blog
3 MIN READ

Announcing GA of the link feature for Azure SQL Managed Instance for SQL Server 2016 and 2019

danimir's avatar
danimir
Icon for Microsoft rankMicrosoft
Apr 26, 2023

We are excited to announce general availability of the link feature for Managed Instance for SQL Server 2016 and 2019. Along with the earlier GA of the link feature for SQL Server 2022, we are now providing the most comprehensive solution for hybrid connectivity and data mobility between SQL Server hosted anywhere and Azure SQL Managed Instance.

 

Overview

 

Azure SQL Managed Instance is a fully managed PaaS service of choice for modernization of SQL Server workloads in Azure. You can enjoy benefits of Azure without moving your SQL Server, by setting up a hybrid connectivity between SQL Server and Azure SQL Managed instance using the link feature. Using the link, SQL Server databases are replicated near real-time to Azure using proven Always On technology. You can run the link for as long as you need it, weeks, months, and years at a time. With the link you can effortlessly make up-to-date copies of your data available in Azure regions, and modernize your workloads by taking advantage of Azure’s scale, performance, and benefits of modern neighboring services such are Machine Learning, Synapse Analytics, and many others. The link feature can also be used to scale your primary SQL Server workloads to Managed Instance, or to offload application read-only, reporting or analytics workloads to Managed Instance as a secondary.

 

Supported SQL Server versions

 

The link feature is now generally available for the following SQL Server major versions and editions:

 

SQL Server version Editions supported OS supported Servicing update requirements
SQL Server 2016 Enterprise, developer, standard Windows Server SQL Server 2016 SP3, and SQL Server 2016 Azure connect pack
SQL Server 2019 Enterprise, developer, standard Windows Server SQL Server 2019 CU20
SQL Server 2022 Enterprise, developer, standard Windows Server, Linux SQL Server 2022 RTM

 

What’s new

 

With GA release we are pleased to announce the following feature updates for the link:

  • Automated backups in Azure for replicated SQL Server databases
  • New PowerShell scripts for automating creation and configuration of link
  • CLI commands are now available for automation of all link operations
  • "Network Test" option is available in SSMS 19.1 to validate network connectivity and ports
  • Automated network troubleshooter is available in SSMS 19.1 in the link creation wizard

Databases replicated from SQL Server using the link feature are now automatically backed up to Azure. All backups in Azure are protected with our industry leading SLAs. Never miss another backup of your on-premises SQL Server databases with automation the link feature provides. Your replicated SQL Server database backed up in Azure could be restored using PITR (Point in Time Restore) to any earlier point in time since the backup is available, and with a minute granularity. Database backed up in Azure could be restored as another database on the same, or another Managed Instance on your Azure subscription. With this feature you can easily create a stand-alone copy of your replicated on-premises SQL Server database in Azure for further use.

 

With fully automated PowerShell scripts we have now made it considerably easier to automate link operations. The scripts will allow you to prepare the environment, create and manage links at scale. We are also introducing the support for CLI commands for customers who prefer compact syntax and similarity with other scripting languages. It is also possible to use any combination of PowerShell and CLI commands if you prefer to do so for all your MI link automation jobs.

 

Integrated network troubleshooting tools in SSMS 19.1 help test the network connectivity and ports during the initial setup. In addition, each time create link wizard is used to create the new link, automated networking troubleshooter is triggered to help with any subsequent misconfiguration issues. If there is an error creating the link, clicking on the error, in case the issue was network misconfiguration related, will be exposed with relevant troubleshooting details.

 

Next steps

 

To learn more about Managed Instance link feature and how you can use it in your scenarios of interest, head to the Overview of the Managed Instance link feature page and follow references to other related articles describing specific aspects of the feature into more details.

 

Share your feature feedback, improvement suggestions, or comments by contacting the product group through Managed Instance link user feedback, or post a comment below.

 

Updated May 25, 2023
Version 8.0
  • Masayuki_Ozawa's avatar
    Masayuki_Ozawa
    Copper Contributor

    Thanks for the great information.

    For Managed Instance Link, a discussion of the upcoming SQL Lincense Free DR when synchronization to MI is used for DR purposes (Introducing SQL Server 2022 GA  Slide 12), but what has happened to this one since?

  • Peter Shore's avatar
    Peter Shore
    Copper Contributor

    Are we able to cleanly failover to MI and failback to SQL Server 2016-2019 like we can with SQL Server 2022?

  • Peter Shore - No, Disaster Recovery (two-way) failover is available for SQL Server 2022 only, and due to technical limitations it is not\cannot be available for earlier versions. For more information see: https://aka.ms/mi-link

  • Mxaris's avatar
    Mxaris
    Copper Contributor

    danimir  what about SQL FCI cluster? Can we build link between SQL FCI cluster and SQL MI?

  • Mxaris - Only partially. You can build MI link on the FCI cluster primary server. However, on the FCI failover, the link will not continue replication on the new primary server. Therefore you can perhaps use it as a temporary solution to replicate data from the primary to Azure, however as a solution that fully works with FCI failover - it won't work. On the other hand, MI link fully supports Always On tech., so if you have an on-prem. AG with multiple nodes and are using the listener endpoint, in case of the failover, the link will continue working seamlessly with Azure. For the full disclosure - we don't require customers to have an existing AG on the SQL Server as the link could be setup on a single node system as well, and without WSFC. Hope this helps.