Introducing Azure SQL Database Managed Instance

Introducing Azure SQL Database Managed Instance

– Coming up we take a look
at a new deployment option for Azure SQL Database
called Managed Instance. Many of you have applications
powered by SQL Server and want to migrate and
modernize with the cloud. There are a class of applications that have complex database environments and require things like SQL CLR, SQL Server Agent, and
cross database queries. In the past, these
dependencies prevented you from migrating to a managed PaaS service. Well, the great news is
that all of these and more, are now supported with the new Azure SQL
DB Managed Instance. That means you have access to the most intelligent database service with zero code changes and
near 100% compatibility. Let me show you how it works. We’ll start by creating a new
Managed Instance in Azure. In the portal, search for managed instance as you normally would. And give your service a name. Select a subscription,
region, performance level, all the common parameters when you’re creating
your database service. Select Create, and within minutes you can
begin using your new service. I’ve already created a
new Managed Instance, so let’s migrate my
application databases to Azure. I have my Stack Overflow Enterprise application deployed locally. This is connected to two databases hosted on SQL Server 2008 R2 in My Data Center, and the application requires
cross database joins to render these views. Let’s migrate our databases to Azure SQL DB Managed Instance. I’m going to use the
Database Migration Service. I start by giving it the name of my SQL Server 2008 R2
environment in My Data Center. The service can also migrate from other sources like Oracle, MySQL, and any supported version of SQL Server. I point it to the Azure
SQL DB Managed Instance that I created earlier. I select the two databases
I’d like to migrate, and finally I point it to a
temporary storage location. The service will use this to store objects during the migration. And that’s it. We’ll give our service a name, and we’re off to the Cloud. The service will begin
migrating my databases to the new Azure SQL DB Managed Instance. It will restore the databases
and all dependent objects. The database migration service supports multiple scale models from megabyte to terabyte size systems with minimal down time. We can click in and view the
progress of my databases, and you can see that
in just a few seconds, our databases have already
completed the migration. So let’s return to our application. Without making any other changes, I’m going to point my application to my Azure SQL DB Managed Instance, and let’s rerun our application. In a just a few seconds we’ve migrated, and our application just works. No code changes needed. And as you can see, our application is now connected to Azure SQL DB Managed
Instance with full support of my cross database joins and all other SQL Server dependencies. No, this is not a virtual machine, this is a managed database service. I don’t need to patch my operating system, upgrade my SQL environment, or worry about any machine configuration. Azure manages all of these and more. It’s durable, highly available, secure, and now I have access to all the intelligent
capabilities I only get by running SQL in Azure. For example, right here in the portal, I have access to a full range
of performance insights. Azure is keeping a history
of my database telemetry, and I can find and easily
drill into those queries that are consuming the most resources. In fact, Azure continuously monitors all the queries being executed. We’re using machine learning to understand the database workload. And we produce recommendations on how to improve performance. I can take the script that Azure provides, and apply this directly
on the system myself. Or, if I choose, I can let Azure automatically
apply the updates for me. Azure can auto tune my database. We are the only cloud that
offers this innovation. We’ve also been innovating with security. Over the years, we’ve introduced
Auditing, Threat Detection, and now we’re introducing
Vulnerability Assessment. The Vulnerability Assessment
will scan my database using a series of best practices, so I can maintain a secure
and compliant database. For example, many of you need to comply with regulatory requirements
like GDPR and PCI. Among many things, the Vulnerability Assessment can detect where I have sensitive data
being stored in my database. It will also include recommended steps to protect the data, and I can take immediate action right here in the portal and apply
a dynamic data mask so that I can limit the
exposure of the sensitive data to end users and applications. So, that was a quick overview of Azure SQL DB Managed Instance. You can learn more by
following the link shown. Try it for yourself, and let us know what you think. Thanks for watching. (energetic electronic music)

Danny Hutson

3 thoughts on “Introducing Azure SQL Database Managed Instance

  1. This is excellent, and has held me back from utilizing SQL in Azure. I'm going to begin testing this today, with hopes of recommending this to my customers in the near future. Great vid from one of my fave channels. Keep up the excellent content.

Leave a Reply

Your email address will not be published. Required fields are marked *