What is it?
We are running out of time actually we got only 15 minutes we got.
It's OK, I can distribute slides Lebron's anyway. This is not slide heavy deck anyways.
Let's get going.
Hello everyone Welcome to my session now modernized on premises. SQL servers to Azure using the Azure Database Migration Service, and my name is Raj Pucci. Raju principle program manager in audio data engineering. My team's primary focus is to enable seamless migrations to other databases.
And the tools and services that we built so today. What I'm going to do is I'm going to briefly touch upon now why we really need to think about migrations to begin with, and then I'm going to showcase the various phases in the migration journey and then I'm going to talk about the specific tools and services that.
To navigate through the migration journey that I'm going to talk about and then I'm going to do couple of demos. One is you know how you can use our data migration assistant tool to do the assessments to make sure that how ready you databases migrating to Azure and then I'm also going to give a demo how to migrate with very minimal.
Most near zero downtime your databases, which are sitting on premises to Azure using the Azure database. Migration service until the time permits. We got only 15 minutes time here. If the time permits. I'm also going to showcase how you can use our power. Shell Commandlets to automate your migrations as well so that you can do mass migration.
And let's talk about you know the reason that why we're here. Actually, why are we really need to worry about migrations at this point so a question for you do you know when SQL server 2008 under SQL Server 2008 R 2 reaching the end of support? I got 3 options there already reached July 2019.
12020. Can you if you know the answer? Can you raise your hands on tell us please?
July 2019, so that's the whole reason. This is So what will happen if it reaches to the end of the support so SQL Server 2800 to reaching July, 9th, 2019. They are reaching the end of the support under of course, Windows Server 2008 and 2008 or 2 are also going to reach.
Porter by January 14th 2020, now, what will happen actually if you don't really respond for the end of these support lifecycle for these products you will not get anymore. Security updates, which is going to put your entire sequence environmental to big risk and then there are complaints.
As well as you might understand you know, Microsoft is really satisfying lot of the compliant certifications to the latest and greatest service products that we have and because customers are running on the old versions. They might not really kind leverage. Those notifications as well. And most importantly, you're going to miss the innovations that are built into the.
Start in the cloud so those are the 3 implications that are there that if you really don't respond for the end of the support now let's think about what are the different options that you have there are 3 different approaches that you can take to handle this end of the support the very first option. We call that as lift and shift to platform as a service.
Is modernizing your SQL servers lifter shifting to the managing distance audio SQL database? Manage instance so arduous SQL database manager instance provides 100 percent compatibility very close to 100% compatibility with your on premises environment with your on premises instance model and also it supports the compatibility levels.
Very latest to the 2005 so if you have a database, which is running on 2005 compatibility level. You can still migrate that specific database to manage instance with very minimal effort, which I'm going to showcase today and then if your workload doesn't fit for a manager instance for any.
That you will know how to find out that using my demo. But in case if that doesn't fit for marriage instance for some reason the next option that you got is to migrate or upgrade to the latest SQL server version, but migrating to a SQL servers, which are running on the Azure VM. So those are the 2 different options when it comes to the lift and shift to the cloud.
The next option is that you can upgrade on premises. You can still stay on premises. But you can upgrade to either SQL Server 2016 or 2017 or in the worst case scenario. You can still stay on premises as it is on a SQL 2008 or SQL Server 2008 R 2 wherever you are, but you need to buy.
Ended support beyond that point that's a separate separately. You need to buy to make sure that you get the security patches in but in the middle. If you upgrade your environment to SQL servers, which are running on the VM even if you stay on SQL 2008 and 2008 or 2 as it is, you can still get the.
3 years for free so those are the different options that you got Watt. I'm focusing today is mainly focusing on the first approach. Where in case if you decide that you want to modernize your environment to cloud. You want to migrate to the cloud, especially to the marriage instance? What is that you need to do that is the thing that I'm going to be main fork?
Presentation here.
Now let's talk about.
What are the different journeys that you have? What are the different phases that you have in the migration journey so the very first phase in the migration journey is called assessment phase. This is the phase where you want to go on the discover your entire SQL server environment. You want to scan across your data state and find out the.
Disease. Which of those applications are referring to which databases on? Which of the applications are dependent on what are the other applications that are there dependent on you know? Which of these applications that that you need to migrate together. You cannot have an application migrated. Another application, which is sitting in the on premises and both have dependencies then you will really run into a lot of.
And everything so you really need to understand what are my dependencies water the servers that the application is running on? What are the SQL servers that databases that I need to migrate? All this analysis happens during the assessment phase and also it tells you what is that it is really needed to migrate these databases to the cloud are these databases are compara bulto?
If not you know what is the effort that is there for me to migrate to be able to migrate to the cloud. You want to understand all this analysis that you need to make during the assessment phase so assessment phase really gives you a good planning for the actual actual migration that you're going to be doing it and today I'm going to showcase specific.
That you can use to really go through this assessment phase and really understand what effort that is required to migrate these databases to the cloud and in the next phase is called migrate face that's the where, you are going to migrate your schema. You're going to migrate your database and as well as any other server level objects.
Objects are outside of your database, the good examples are SQL agent jobs and SSIS packages in a logins. Windows logins and as well as the SQL server logins. You have linked servers. You know how do you want to migrate these things to the cloud and it just because you migrate your database that doesn't mean that your applications are going to function you still need to make sure.
All the other objects that are really, that your application is dependent on needs to be migrated as well. And that's where I'm going to showcase a demo using our database migration service? How can you really migrate all these objects to the cloud?
The third phase is optimized phase where you know once you migrate to the cloud. That's where you're going to keep thinking that you know how can I further start leveraging the native cloud services to bring more efficient experiences to my customers? How can I save cost more. That kind of analysis happens on the optimized phase once you migrate to the cloud and at the end.
Managed security something that you don't really consider that as a last phase security. You have to think through the security from the very beginning. You know how can I secure my environment? When I migrate to the cloud that is something that you might want to think through the entire journey and then manage manage is obviously how can you really use the cloud?
Change the efficiencies of your databases how databases functioning is it properly running how available these databases. Those kind of monitoring that you can do during the last phase so in this presentation. I'm going to be focusing more on the assessment and as well as the migrate phrases make sense.
So now let's think about the specific tools and services that our team built over a period of time that really helps you to take you from assessment phase migrate face to the cloud. So I'm going to go from left to right here on your left side. We kind of listed all the different types of sources that we support migrating from.
So what we call that as a homogeneous sources. We support all the way from SQL Server 2520, 17 that you can migrate to either a SQL database. Singleton elastic pools or you can migrate to Azure SQL Database. Manage instance or you can migrate to SQL servers, which are running on the Azure VM and you really want.
I understand where can I go is my is my workload is good fit for SQL DB Singleton or is my workload is good fit for Sicario sequel database for marriage instance? How do you know that that is something that I'm going to showcase a demo that how you really make that kind of addition as well, and we also stop support migrating from heterogenous sources.
Databases, which are running an Oracle Sybase. DB 2, etc to the cloud targets. We also support migrating from open source is my SQL postgre SQL to uh do SQL database for my SQL, Azure Database for Postgres SQL as well, and not only that we also support migrating from no SQL databases.
Download eBay to Cosmo DB under support for Migration from Cassandra to Cosmos. DB is coming very soon. And then we also support not only the on premises sources. But we also support migrating from other cloud vendors like AWS. You can migrate in the SQL servers, which are running on the audience.
Any of these target platforms that I mentioned there, you can also use our service to migrate from SQL server, which are running on the C 2 on AWS site to the target environments that I mentioned and you can also migrate from Google Cloud as well. So these are the spectrum of sources that we support and the right side you see the the set of targets.
Migrating from some more source and target pets are going to come in feature but now we have a very broad spectrum of sources and target page that we support using our tools and services now that we understand the specific source targets that we support. Let's talk about assessment phase so go back to your migration journey, the very fast.
That is an assessment to help you to go through that assessment phase. We have a tool called data. Migration assistant tool? How many people know about that. All have used that so we really sorry for the first time in 2016 August timeframe. Since then do you know? How many databases that our customers really assessor using using that tool since?
2000000 databases.
Customer success are 2000000 databases using the toll to really understand what it really takes to migrate these databases to the cloud. So it will give you the migration blockers. It will give you the breaking changes that things that are going to break if you migrate. It also provides you the target recommendations a lot of customers are getting confused now because there are so many options.
Am I good fit for SQL DBA Singleton am I good fit for inelastic ports do. I need to migrate to am I or do I need to migrate the VM? What is the target. That is going to be good fit for me that really matches with my on premises workload with a minimal effort that I can migrate all that analysis that can.
Under DM really help you in that front and then when it comes to the migration and before I go to the migration. There is another tool called SQL Server Migration, assistant or how many people know about that.
So SM ES is pretty much customers used to access on my great, especially when they're coming from the heterogenous platforms. Like Oracle, Sybase. DB 2, where that's where you need to really convert the schema migrating from a foreign platform. I call that from a computing platform rather than a different platform to SQL server is not an.
Because you want to make sure that you transform the schema, which is compatible onto the target so SSI may really helps you to transform that schema and also sometimes it also auto transforms your schema. It exactly knows how to convert some of the schema there and then it also helps you to migrate as well.
And then that is the part of the assessment so we also have a tool called the geodatabase experimentation. Assistant to lot of customers really, really scared as a matter of fact to see how my workload is going to really respond. When I migrate to cloud. You know how to how is my response time? How is my response time to the mission critical business functions so that?
Used to do that kind of analysis, so basically you can you can call that as an AB testing tool where you collect all the performance data from your on premises workload and you replay the round. The target and then we will give you a comparative analysis between how your queries workload is responded on the source versus the target, we give you a comprehensive.
So the queries performed on the source versus on the target? Which of the queries are performed better which queries performance poor and which are the queries failed that kind of components of analysis. We give out of da so that you will get some kind of a confidence on how your workload is going to really respond even before the migration happens.
Assessment phase and when it comes to the migration phase audio database. Migration service is a fully managed service on the Azure? Which customers used to migrate the database is from on premises to the cloud. What is so great about Azure database. Migration service actually so here you saw the source and target page that we support we support.
Migrations and we also support heterogenous migrations under the Migration Services, a fully managed service on the Azure. You don't have to worry about managing my service is fully managed in the Azure. It provides a Rita orchestration capabilities, where you can really create a migration project under group together the databases, which are.
So if you have a class database reference of queries. There are multiple databases that you need to migrate along with your application. Then you can group together. All those databases. Today, single migration project and then you can migrate the entire project as a whole and then it also provides a scale migration approach. You know one or 2 migrations. You can do with the Y button.
A customer who wants to migrate thousand databases at the same time, you really want to automate. Those migrations using the Powershell Commandlets and as well as the rest rest rest. APIs that we provided you can really automate those migrations as well. I have a customer in South UK who migrated 8000.
From Rock Space Data Center to do SQL database using this service and pretty soon. We're going to be releasing that as a case study how they did it so every week. They grouped together 400 basis and the automated proportional script using using the power. Shell script that we provided out of these services and then just they prepare all that homework right. They do all the homework.
Time during the weekend and they just hit a single button, saying that my great and it will take care of all those databases. So they group 400 database. This is a real customer experience actually so they migrated around 8000 databases to to Azure SQL database. I have another customer. I'm currently working migrated thousand databases in a single migration window, they only have one single migration win.
Weekend they need to migrate all these thousand databases in a single time frame. So we're going to working with them how they can really automate these migrations as well.
And more importantly, it provides a near zero downtime migration experience. We understand that SLA migration. Slas are very critical so lot of customers. They don't have a lot of down time when it comes to the business critical apps to migrate for them. We provide online migration experience, which I'm going to demo as well. I know I'm going real quick here is because.
But you show the that the most as well. If you have any questions, please raise your hand and ask at the same time.
Now let's let's get to the demo, So what I'm going to do is let me quickly check the time.
To give you a context here.
I have the double code, which is running on my SQL Server 2008 R 2 instance and I got couple of databases, which are on the inventory and I want to migrate these databases to the cloud. But I really don't know whether I can migrate to do SQL database. Singleton databases or whether my workload is good fit for Azure SQL, database for.
Before marriage instance, so I don't know at this point. All I know is I know that I want to migrate to the cloud. But I just don't know my target, which is good fit for my workload so I'm going to use my DM. A tool to perform that kind of analysis and hoping that the DMA tool will tell me which target that I would choose.
So I already installed by DMA DMA tool is publicly available free. It is, you can download it from the Microsoft. Download center and it is a desktop door pretty close to the sources. Wherever your sources are there when you install the DMA told the very first thing is you got to create a project?
Whether you want to do in assessment or migration, so at this point. I want to do in assessment. So I choose an assessment as my project type and then I'll give some name to it.
And then it first what I'm going to do is I'm going to choose SQL databases. My intended target. I don't know if I'm going to migrate to SQL DB or not, but I just want to see what it really takes to migrate to SQL DB is my database is ready or not so I create that product here. There are a couple of options here check database compatibility and as well as check fee.
Compatibility is it's going to scan across your schema and find out if there are any old style syntax that might not work on the targets anymore, especially customers who are running on 20052 thousand 802 they might be using some legacy syntax, which is not being supported anymore. So you want to understand what are those objects that are getting impacted under how to fix them?
Something that you can find out in the compatibility analysis. There is another option called check feature parity as well. That means you go beyond your databases on find out are there any other features that my workload is using that I need to worry about outside of your database for example agent jobs link link servers.
Are these objects are supported on the target or not? That is something that you might want to understand as well so you choose. Those 2 options and then you connect to your target the source. This is your source environment. Actually, we support both windows authentication and as well as a SQL server authentication. You connect to it, then it will pull out all the databases that.
You need to analysis so let me check my connectivity here.
See, I don't have my VPN, let me start the VPN going on.
But that's OK, so I cannot really connect right now, the VPN is down so.
But the good thing is I kind of anticipated this to happen little bit. So I already did a couple of analysis here for the same source of databases. I did 22 assessments here. One is for SQL DB and one is for SQL among the reason I did 2 assessments is because I want to understand whether I go for MI or whether I go for SQL DB.
This point, so I'm going to choose my SQL, DB one and I open that assessment. It shows that there are 4 features that are not supported on the target at this point, the most famous example is crossed database. Referencer queries a database. A query, which is sitting in one database if it wants to retrieve the information from a data.
Just sitting in a database tool that is called across database reference inquiry because you're going from my context of database one to a contact stop database 2 and that is not supported on agile. SQL database right. You know that right cross database reference. Wearisome not supported on ledger. SQL database, the next alternate to use is to use the.
So there is a new feature called elastic queries in the Azure so that you can create that as an external table and then make the external table reference to the the table, which is sitting on the database, too well. If it is one hour to stored procedures. That's fine. I can do that. But I have a customer who got 2000 stored procedures in a single database.
They need to fix all those 2000 stored procedures by by using the elastic queries. When I propose that recommendation to the customer. They really laughed at me, they lawful for almost 2 minutes do you expect me to fix those 2000 stored procedures to migrate? I'm not migrating? I'm going to go to VM right and then service broker.
Classic example SQL server agent jobs is another classic example that it is not supported on the Azure SQL database. Singleton databases are elastic pools. So you got bunch of items that you need to fix it. Before, you migrate to Azure SQL database. Let's now think about the same assessment, which run on marriage instance right. I'm going to open up that assessment.
No feature gaps all the features that you just talking about are currently supported on a mile. The whole reason that we gotta might right. We want to make sure that you can be able to do a lift and shift a migration to the cloud without any effort that you need to do right again by intent here is not to tell you that you always migrate to.
Intent there are so many workloads out there there pretty good fit for SQL DB and elastic pools. The same customer UK. Based customer that I made a reference who migrated 8000 databases. They migrated to SQL database elastic pools. So a lot of what loads out there pretty good for SQL DB and SQL DB elastic pools. My intent here is only to showcase.
Can use the DMA tool to really make that kind of differentiation to make that kind of addition whether your workload is good fit for SQL. DB WhatsApp marriage instance right? That's the only intent that I got but I'm not really suggesting that you always go and migrate to a my SQL. DB can be a great fit. You just need to understand so that's how you can use the DMA tool to read.
Where can I migrate to write good so how about the compatibility issues you still need to address the compatibility issues no matter where you go whether you migrate to SQL, which is running on the VM or even if you upgrade on premises from the old version to SQL Server 2016. You still need to work about the compatibility issues because these are the very old syntax that is being used.
Sex is not supported anymore, so you need to address some of those objects that are reported. There, there. There are multiple categories. There, the breaking changes, which means is that if you don't fix this stored procedure after the migration when your application makes a difference to this specific object. It will fail, so you need to fix it? How do you fix it we provide a recommendation?
For example, non anti joints, we give an example how you can convert the query using the standard ansi joins so we will try to give you a conference of recommendation to fix it. So breaking changes are the highest priority that you need to work on the next priority that you need to work on behavioral changes so those ones will work still continue to.
The behavior could be changing. That means in this in this example. You know the query might still work. But you might experience some performance degradation because of the changes that we made for the optimizations or the query optimizer right at that point you might want to take a look at it and see if we can fix it. The informational one so you don't need to worry about it. These are called Depp.
Deprecated feature means the feature works as expected still works. We might remove the support for future releases so for the sake of the migration. You don't need to really worry about it. It's still works fine. The only thing is if you start new development on the target. That's the time the time that you might you might do.
Those features anymore, but Microsoft also promised to not to introduce any compatibility issues anymore because we want to make sure that you don't really have any difficulties to migrate so going forward unless it is a security threat unless a specific feature is a security threat. We don't really discuss discontinue the features anymore.
Or that you are in the latest versions of the SQL server. You know you have better opportunity to migrate to the cloud as well so that's how the classification is done here, but we also provide different compatibility levels, even if you migrate to the SQL DB or manage instance, you can still keep your database at lower compatibility level.
For example, you're migrating from 2005. You can still keep your database at 2005 compatibility level while migrate into the cloud. If that minimizes your effort to migrate the great example is if I go to compatibility level 100. I only need to fix 2. Breaking changes but whereas if I put my compatibility level all the way up.
Then I need to fix 3 of those right so we give that kind of you for you to make a determination whether which compatibility level that you want to keep after migrating the database to the Azure. In this example. There is only one difference. But they know in your case it could be more so make sure that you look at the breaking changes make sure that the specific compatibility level that you.
Use make sure that what target that you want to migrate now once you know your target in this case. I determine that I want to migrate your mind because I don't need to worry about any feature parity shoes at all, so because my shows that I have a zero.
Feature parity shoes, so I determined I decided that I want to go to my great am I at that point in the next question comes what is going to be my size because SQL DB SQL DB elastic pools? Am I comes up with a lot of tears, and Skews and you want to understand where to start go ahead question.
Yes.
It available the question is, is the compatibility level available nodule. SQL database as well. Yes, it is available in module. SQL database as well. And both Singleton and as well as in the elastic bolts. You can migrate to Azure. SQL database and you can keep your database lower compatible level as well. It's not just limited to MIT.
Now the question comes what is the size if I put a very large skew right now. I'll go to the highest Q that? I got great, but you end up with paying more unnecessarily. You're ending up with paying more. And that's going to defeat the whole purpose of migrating to the cloud well. I'm going to go to the lowest. Q then what will happen. You're going to suffer the performance.
Mediants after the migration is done is going to be very bad, then what is my optimal cue that I want to begin with, and how? Can I find out for him for my workload that's where the DM is going to further help you so we, we published an article here that I'm going to go to that article here very simple when you install it.
Power Shell script take that power shell script and then execute on this source. It will do a lightweight performance collection very lightweight performance collection using the performance counters and then take that output bring that output back to us and then give that as an input to the DM at all, then we will produce produce user HTML report for.
Typical HTML report is going to look like this for a given assessment that I just learned this is how it is going to propose for a given database. It will tell you that specifically are that we think it is optimal for you and we also tell you the specific skew as well. Not only that it also tells you the specific cost? How much it cost monthly for you so you can have a nest.
Right we think that this is a good fit for you to begin with, and as you run your workload on the cloud for next 3 to 6 months. Then you can always leverage. The intelligent features that are built into the cloud. The SQL DB itself will tell you that. Hey, you need to upgrade your skew or you need to downgrade your skew it will tell you but at least for first 3 to 6 months.
Recommendation here to start your skew question there.
I'm sorry.
You can alter it as well, yeah, you can write that.
And then not only that you know think about the same example where the customer is God thousand databases that I'm working am I going to do create these thousand databases individually. It's going to take a very long time, So what we did is we also give an option here we can generate the power. Shell script or a provisioning script using all the confirmation that we did, and then you just run that script on.
It will create all those databases for you, using the same tier on this queue that is that is being defined here. So it's completely automated, so it's not easy actually.
So now.
Now basically we, we know which target that we want to migrate. SQL am I. We know which size that we want to create what is the next step.
What is the next step you just migrate right you know everything now you know which objects that you want to fix you know which target that you want to go. You know what size that you want to go. You already created their target using my scripted provided here. The next step is to go with migration so for Migration. What I'm going to do is I'm going to use my other database migration.
But I'm going to.
I'm going to give a demo for online migrations so before I go give a demo for online migrations. I want to explain how the online migrations works. I specifically took an example from migrating from SQL server to manage instance that is an example. So you have your on premise environment here and then you want to migrate.
To manage instance on the top in the cloud and you will be using my Azure database. Migration service to migrate so in online migrations for my we use backup and restores so we take a full backup. We restore it and then we take subsequent T log backups and then we keep on applying those T log back.
Until you say that you're ready to do the cut over so you provide those backups in the assembly network share and we upload those backups to the blob storage under we restore at first. We restore the full database backup and then we look for any any incoming T log backups. The soon that the backup is available in the SMB network share we upload to the blob storage and going to be restored.
Sing it forever until you say that I'm ready to do the cut over when you're ready to do the cut over you will stop all the incoming traffic that is coming into the source and take the final log backup. We call that is that a log backup and then provide that log back up to the SMB network share and we upload we restore that will tell you that that backup is restored at that point.
When you do the cutover will bring your database online. So, your typical downtime really starts during the last phase when you're ready to do the cutover where you stop all the incoming traffic to the sources that is the only time that you have your down time so you would typical downtime looks like the time it takes to do the final log back up the time it takes to up.
Log back up to the blob storage and the time it takes to the to restore your log back up so that's the only time that you have the down time typically it could be like 15 minutes time right if you really want to further reduce it. We're going to work with you to increase the frequency of your log back up so that your log backups are going to be smaller and smaller towards the end of the migration.
And then it's going to take last time on that right, so I'm going to show this on live.
So, in order to do migration using the other database migration surveys. There are 3 different steps like I said, first of all. You need to create the DNS service if not creator already so just like any other module services. You need to provision. Our service at first, and then create a migration project, and established the migration between your sources and targets and then keep going.
And you will do the cut over so that is what you are going to be doing so at first. Let's look at the service creation experience. The DNS service creation experience, so like I said it is a nodule fully managed service, you go to the portal. The Azure Portal and then click it create resource link here.
And then look for Migration.
And you find a database migration service, there and then you hit a create button here.
And then you give it.
Name for this service for the DM S service.
And then you pick a specific subscription where you want to create your service. We usually recommend that to create in a subscription target. So basically wherever you are. My instance exists. Wherever you Roger Audio SQL Database. Manage instance exists typically choose that subscription so that they can colocate each.
That way you can have an optimal migration experience as well, and then you can choose the resource group where you want to want us to keep the D Ms Resources, and then you choose a location where you want to create the DM S service again choose the choose the region, which is close to this target that way your migration experience is going.
Much faster and then the next day is very important step, creating about tool network are choosing the right virtual network. So let me choose a different region looks like I don't have the?
The right virtual network there.
No South devices out central here somewhere.
Yeah, so this is the most important step. The reason is that the way that we the DNS service, which is sitting in the cloud. The way that it is going to connect with the sources through the through the net that you're going to associating here. So we need to make sure that we have a site to site connectivity between ever larger network and on premises net.
It can be done in 3 different ways, either you can have an express route connectivity or you can have a site to site VPN or you can have a point to site connectivity. So to really explain how this network topology is going to look like we have a document published that has this information here, so there are 4 to apologies that are described in.
I'm going to touch upon couple at least so here this is the on premise environment your SQL server, which is sitting on the on Prem and you want to migrate to manage instance here and then you have the DNS service that you are going to use to migrate so basically the been at the instance got all.
Also has a expressed route gateway connected to the on premises.
And now I'm going to create the DM S in the same peanut but I'm going to use a separate subnet so you can create multiple subnets in TV net right you guys know that a subnet is the sub range of the IP addresses. That IP addresses that you have for the Internet. So you have to have a dedicated subnet forum, I instance.
Any other resources in the same subnet that is being used for my instance, it will not allow you to do that. It's a security restriction. So you have to find out another subnet in the same B net that you can keep your DM S instance out there, so that's what I did so I created a separate subnet here and then I put DM S in there and I got my am I in.
Undis been at the whole bean it has got Express Gateway, which is connected to the on premises so that way. The D Ms can connect to the source and as well as to the target makes sense and more simpler approaches. What if your sources already on the Azure VM. If you're running SQL servers, which are running on the Azure VM.
Roger BM is also in the cloud so there is no express route requirement out there, so you use the DM S same, Vineet as of the VM and also you can use the same B net for MI? Which is different subnet and that way. The D Ms will contact both the source. VM might as well as the target on my instance, so those are the 2 different apologies that I explained.
I always recommend to go on then check this topology document to be able to properly configure. My instance, there and then we also gave a list of outbound security rules inbound security rules that you need to configure for your NSG rules. So this is a very vital documents that I always recommend customers would do it if you choose a wrong be not here, though.
After the DMV services creation, you cannot be able to connect to the source and that's where I see a lot of customers are running into issues with my service right now because they're choosing the wrong vineet. The Peanut, which is not connected to the sources or the Wiener not connected to the hammer instance, so we want to make sure that we fuck. We pay attention to that and Presenti run let me.
Find out the size of your DM service as well. So there are 2 different tiers that we got standard and premium standard is always free. You don't need to pay for the Ms service at all for standard and standard only allows the offline migrations. That means your migration. Downtimes thoughts from the time that you started your migration so it's a?
I'm sorry bigger downtime window for a lot of customers. It's OK because they have a weekend down time you know if it is like one terabyte of data base. I can easily migrate. I don't need to pay for DMV service. I can just simply use the standard skew and then I can get away with that. But we also have a premium SKU premiums. Q is mainly meant for online migrations to minimize.
We have zero and today we're going to use the premium skew to showcase the demo under under this, this premium SKU also.
Is going to be free for the free for the first 6 months? I need to have some text there. But if you use the premium skew it has 4 record under 4 record is free for the first 6 months since you create your DM S instance right so you can use that time to really leverage your migration so that you.
Anything for migrations if you start using the DNS service beyond the 6 months, then we're going to start building building that make sense any questions on the pricing. No confusion right so I'm going to choose my premium. We're going to be planning to add more excuse to the premium premium tier so that for example, 8 16th.
Use at the time if you choose those once they always build. But if we choose only the 4 week or in the premiums here that will be free for the first 6 months since you created your DM S instance.
He chose that and then you go and hit the create button so usually the create will take around 8 to 10 minutes. So I already created in my service here, which I'm going to use it, which is demo DM S online. Vesta us too. That's what I kind of named it and then I got bunch of migration projects that I already created but for now, let me create one here.
For this demo so I'm going to do SQL bits demo.
And then my sources SQL server, and I want to migrate to Azure SQL Database. Manage instance in this source like I said, we support all the other sources as well that I talked in my tools slide and then I'm going to use online migration experience, not the offline so save it.
And I'm creating it.
Now the very first step is I would provide my source information here. The source SQL server, which I'm going to copy it from here. This is my source. SQL server, and we support both SQL authentication and windows, so I do windows authentication.
So at this point, the DM S is going to try to connect to the source using the B net that we provided during the creation of the DNS service and then make sure that it's going to validate the user has the right permissions are not and now the next step is you provide an application. ID application ideas and new concept in the Azure Active Directory, where we generate an application.
Access credentials to that application ID, so that any cloud resource that you need to access. We will use the application ID to do authentication so for example, here, the sequel. Am I, which is my target is a cloud resource under the storage account of the blob storage account that I'm going to use to upload my backup files is also a cloud resource.
So this cloud cloud resources. I'm going to use app ID and if you don't know how to create an Apple ID. We provided a step-by-step guidance here that really helps you to create the app. ID there so for the sake of the time. I already created an app ID, so I'm going to use that.
Here is application ID and then I'm going to use the key here.
This is my key and now I want to pick up the subscription where Maya my instances there.
So this is the place where I got created via my instance and then I'm going to pick my uh. My Insteon switches private body and then I'm also going to give the?
Password and user for MSD.
For their my other I'm going to save that information. The next step is I'm going to select a specific databases that I want to migrate?
Well, that is doing I'm going to copy some of these.
So either you can you can migrate the entire SQL server as a whole? Which is alliteration to migration obviously or you can pick a specific database that you want to migrate in this case. I'm going to choose which are as my example save it.
Remember, the network share the SMB network share that I mentioned we need to make sure that you provide that network share from which I can pick the backup files so this is the one and you also need to provide a Windows account to DM S.
So that it is going to impersonate that account to read the files from the Assembly network share to upload the blob storage.
Under specific permissions that you need to go for that network share. We kind of documented there as well. And then you pick. A subscription where I can pick a blob storage that that I can upload the backup files to.
And then here is my storage account.
And here in the advance settings, you can rename your database on the target if you want to so which are.
I'll put a sequel bits for now.
And I save it now again. It's going to validate it's going to validate all the information that I provided there. Make me shoot that there simply network share has got a proper permissions to upload to read from the backup files all that stuff.
Run in the final state just do around migration.
And then it's going to start the migration now, So what it is going to do right now is it is going to read all the backup files that are available on that network share and then start uploading those backup files to blob storage and then it's going to restore during this time you would sources still online. So I can go back to my source. I can still really connect to the source my source is still intact.
Right.
So I'm going to refresh here, making sure that I have the VPN connection.
No for some reason there is no VPN connection. So so here I'm going to refresh this again.
Now let's see the status of the migration so bunch of full database. Backup files exist. There is one full database backup file there, which is the which is this one.
And then I got a bunch of log files that are already available in the blob storage and then right now, it is uploading them once the upload is done. It is going to start restoring it. You can really monitor the status here. You know what is happening with migration it will take some time because it has a lot of files there? It has to upload and then back up you will know.
It also tells you what is the last time that the transaction is applied onto the target so that you would know you know to? What time that your source your target is single with your source and it also tells you which backup is restored. So it's already storing it is restored. Several backups and now it is restoring the final backup, which is a tent back.
The log backup right once that backup is also restored then you will know that all the backups are stored and now once you're ready to do the cut over you go back to your source and stop all the incoming traffic take the final back up and make their backup available in the SMB network share come back here. Then you refresh it. You will see the status of that back up as.
I'm I'm not doing all that operation here just refresh this. Now it is still restoring the 10th one, but you can do is start cut over once everything is done so in the cutover will tell you over the final one is also restored. I guess so it is restored now. You can go back to your sources and cut down all the traffic take the final back up and.
To see the final backup status and if it is also shows that it is restored. Other point you're ready to do the cutover so in the cab driver make sure that the spending backups are zero. Otherwise, there are seams. Still, there is one or 2 log backups that are restoring and if you do a cut over at that point of time you will lose the transactions. You will lose the data because we don't really wait until the.
Backups are done will just stop the migration right there and we bring your database online so that's the reason you want away. Make sure that this is zero and then you confirm it and applied so the cutover happens now during the cut over what we do is we bring you a target database online and then you can start changing your connection string so that the.
So now point to the new target that you uploaded you migrated right? That's how the migration work, so with this. The down time is only the portion where you cut down your incoming traffic and then the final log back up. You know how long that would take to restore that is the only time that you have down time and if you want to further reduce that down time you do a PC migration.
Our migration window, let us know we're more than happy to help you to further improve your migration downtime experience as well. There's only one minute left so that's kind of answer my demo there.
So these are the different source target page that we support by the end of hitch to fine line all the entries that you have tick. Mark 3 that will be supported. Those migrations will be supported so we as you see here we got we got a very.
The very widely stuff all the source and target pairs that we got and finally the road map. One important thing that I want to call out hyperscale migrations, so there. My instance is going to start supporting hyper scales up 200 terabytes of data bases. Now we're going to be enabling migrating those large databases as well. We call that as a hyper.
By integrating with the data box how you guys know data box.
Data boxes and appliance that we can ship to the on premises where you can copy those initial backups. If it is like 60 terabyte of DB you cannot really copy the 6060 terabyte on the network. It will take like one month right you can ship that file using the appliance and then we, we know as a DNS service. We know that the file is already there, so we restore it under we.
Under capturing all the log backups as well, and then once everything is restored. Then you can do. The cut over so that integration is coming that is definitely. I want to call out if you are interested with logic databases. Please let us know we can put you into the preview mode as well so with that. These are the different links that we have that you can really leverage the documentation.
Obviously we run out of time here on, please fill your evaluations as well because we're going to use that for.
This one thanks.
Make sure that you submit our your evaluations to us so we, we used to improve our quality of the products and as well as the presentations. Thank you so much for your time.