Database migration is a fact of life in cloud computing.
And to explain the best and easiest ways to do this Laurent Bugnion is here to
rescue you.
A senior cloud advocate with Microsoft Laurent knows the ins and outs of how
your data can go from on-premises to the cloud from development to production
and from unmanaged to managed or using Azure database migration services and all
delivered with a delightfully French accent.
[inaudible]
so you well we're here at Ignite, and you did a session. Yes, no,
the day before yesterday, yesterday.
In fact it was yesterday on what's the database migration? Yes, it was a,
so we have a those, uh,
so-called learning paths that we prepared where each learning path has five
sessions and a learning policies sessions specifically like super related to
each other,
but the easy tells story and we always use the same application to go there.
So there is also some branding. It's as a tailwind traders application,
which are in the meantime it's starting to become famous. Whereas yeah,
is a stories that a, you know, tailwind traders, acquired Northwind.
And so Northwind is a big data store. And, uh, and of course very traditional.
I used to joke and say that the, you know,
the service literally run under the CEO's desk, right?
So a note in the cloud at all and the tailwind traders wants to put everything
in the cloud. They want to, uh, to, to modernize their application really.
And so, um,
the session I presented and the one that I prepared the most was around moving
your database to the cloud. And so the idea there is that this application,
it's a web app,
app service with asp.net core and a react JS front-end,
uh, that is taken care of. But then on the on premises,
we still have a Mongo DB database running on Linux for the shopping cart.
It's a no sequel solution,
which is of course great for these kinds of applications. You'll be encouraged,
these kind of things. It's very fast also, etc.
And then we have the product description, which is in the classic sequel,
but since you know, Northwind is a, is an old fashioned firms.
So to prepare the session,
I literally took the oldest version of windows server I could still find,
which is 2012 I was hoping to go to 2008 but we unfortunately don't run that.
So we simulate that those VMs as OCMs actually run on Azure of course.
But we simulate that they run under the CEO's desk like I was saying.
And then in the course of the session I show how to use a new service that we
launched last year, which is called the Azure Database Migration Service. Okay.
And the DNS in short a is able to migrate the between different sources and
different targets. So if it's sequel,
we can migrate you directly out of AWS. For example,
if you want to go to Azure instead out of Oracle into sequel for example,
or simply out of sequel server on premise to Azure sequel database.
And we also support migrating from Mongo DB to cosmos.
The nice thing is that it's very managed. So even if you have terabytes of data,
it's going to take time obviously, but it is going to do it in a managed way.
You can even manage the throughput, for example,
if you don't want to choke your targets over, you know, um, so it's a,
it's way more efficient than the backup and restore, which we still support.
But we recommend going to a more managed option as long as the DMS is running,
it's going to migrate the data,
but then it's going to keep the source and the targets synchronized so you can
migrate at your own pace. You can, for example,
play a staging environment on your staging website, you know, on your,
on your new new data to make sure that it's running all these times a data is
synchronized and then when you're done,
you switch your connection string and then only you shut down the DMS because
you don't need it anymore.
So that's a really nice solution if you don't want any downtime yet during your
migration. Yeah.
If you just want to start with the DMS and you have your own database,
create a database migration service at the name of the service. Uh,
you just, you know, into the, is a usual write subscription name,
a region where you want to run that as.
The only thing that you need to be careful about is that you can create a
maximum of two DMS instances per subscription and region,
but it really literally doesn't matter because since one,
DMS can have multiple projects, you don't need two, you just need one really,
unless it's a special case.
And if you should need threes and you have to put it in, in another region,
so that would be a final as well. Yeah.
[inaudible].