{"id":30012,"date":"2020-03-24T09:00:35","date_gmt":"2020-03-24T16:00:35","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/?p=30012"},"modified":"2024-01-22T22:51:24","modified_gmt":"2024-01-23T06:51:24","slug":"azure-sql-database-managed-instance-vs-sql-server","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2020\/03\/24\/azure-sql-database-managed-instance-vs-sql-server\/","title":{"rendered":"Azure SQL Database managed instance vs. SQL Server"},"content":{"rendered":"
As organizations face increasing pressure to modernize their applications and infrastructure, the benefits of the cloud have become impossible to ignore. Fortunately, Azure SQL Database managed instance makes it easy to move your SQL Server workloads to the cloud. Nearly 100 percent compatible with the latest SQL Server on-premises database engine, this fully managed service allows you to use the knowledge you already have to run SQL Server in the cloud. You can learn more about the benefits of Azure database capabilities in the e-book Future-Proof Your Data Infrastructure with Azure: A Business Case for Database Administrators.<\/a><\/p>\n Let\u2019s look at some of the differences between Azure SQL Database managed instance and SQL Server, as well as how to migrate.<\/p>\n Azure SQL Database managed instance is a fully managed SQL Server Database engine instance that\u2019s hosted in Azure and placed in your network. This deployment model makes it easy to lift and shift your on-premises applications to the cloud with very few application and database changes.<\/p>\n Managed instance has split compute and storage components. You can have compute nodes with 8, 16, or 24 cores. The nodes work with database files stored on Azure Premium disk storage. Every database file is placed on a separate Azure Premium disk, and a separate backup mechanism ensures that if something happens to the files, the platform can still restore files from backups. In addition, redundant passive nodes are used to fail-over compute instance if needed.<\/p>\n Because it\u2019s in the cloud, managed instance gives you the ability to easily scale up and down. For example, you can create a managed instance with 16 cores and 500 GB of storage, and then increase or decrease these numbers with the click of a mouse, depending on your needs. Any change you make takes effect almost instantly.<\/p>\n Migrating to the cloud with managed instance is easy. The simplest way to do so is to create a backup of your on-premises database, move it to Azure Blob storage, and restore the database on managed instance using a standard RESTORE DATABASE \u2026. FROM URL T-SQL statement. If you need to minimize your downtime during the migration, we suggest using the Azure Database Migration Service.<\/p>\n Azure SQL managed instance runs in your Azure Virtual Network (VNET) on a private IP address. There are several ways you can connect to managed instance.<\/p>\n Moving to the cloud doesn\u2019t require extensive training. You can get all the benefits of running SQL Server in the cloud with the skills you have today. Simply leverage Azure SQL Database managed instance to do a lift-and-shift migration of your existing on-premises SQL Server databases.<\/p>\nSQL Database managed instance: Under the hood<\/h2>\n
Scaling managed instance<\/h2>\n
Migrating to Azure SQL Database managed instance<\/h2>\n
Connecting to managed instance<\/h2>\n
\n