Modernization Hub

Modernization and Improvement
Azure SQL DB Managed Instances – Built to easily modernize application data layer : Build 2018

Azure SQL DB Managed Instances – Built to easily modernize application data layer : Build 2018


My name is borko bovakovic. And in database systems you are Building relational database services. Sql service, sql Service virtual machines are fully managed database s and Services in cloud. The real of program manager is Actually to be a customer advocate in the engineering team We are talking frequently to customers we tend to understand Their requirements and to translate these requirements Into the full functional services. I have been at Microsoft for almost 8 years. I work on several sql serve he Releases including 2016 which was the biggest one for me that Familiar with some of these. In today’s session we will talk About the new extension of our database is service as a sql Database. Basically i would like to give you product Overview to explain what managed instance is starting from — Let’s stay the modernization opportunity aspect and then Going into detail product overview and characteristics Trying to focus a little bit more on the developer Perspective what does it mean for a develop for work with Managed instance. The large portion of my session Will be demo and then finally if time permits i will talk about The business model. We can also answer the questions you have. Now, before we going into the details i would like to ask you A question of questions to answer the structure of the Audience. First of all, how many of you have been directly Working with the sql server in any form? Okay. That’s great. Sql server in in Azure? how many of you are in the dba role? not many. How many of you are actually like focusing on the database Development? any data architects? Okay. So it is a mix. Interesting mix. So let’s start with opportunity aspect. Why we Are building managed instance. I will try to quickly cover what You probably heard several times but this is really very specific Moment in the technology history when technology plays an Important role in shaping how companies grow their businesses, How they innovate. So definitely an important part of That is transformation. As a reaction, companies are Building digital strategies that include several aspects. And one of these really important aspects is how to get To the cloud because today being come pet and getting ahead means Getting to the cloud. Companies do that really fast. Now, more specifically, to the businesses that are run on Microsoft stack and sql server for the data driven publication, We have seen this stuff towards Cloud being more efficient for it sectors within campaigns. Companies. That definitely has to do with Some strategies that our customers define on that journey And they have seen that customers who are running many Application today in sql server or planning to develop new Application they are getting — they are proposing this approach For cloud immigration. First of all they focus on the Tail application and muscle and migrate them to the cloud. That way they eliminate time spent on managing these Applications which will definitely free up resources in These campaigns and give them more time to focus strongly in Business application, to modernize them by moving in the Cloud and extending their right. So this is a playbook for many Of these companies that we are working with. More specifically to sql server what does it mean? 30 Of database run on sql world wide. That is a huge Opportunity for modernization. Then a huge portion of these Applications run on an older serve of sql not that recent. If you combine those 2, world wide when it comes to Modernizing sql, there is a lot of opportunity. What should be the answer for customers who are considering Cloud migration and modernization? that is definitely a sql Database. It is by far the most and most Economical cloud destination. Why? a sql server that is Reason and operated by microsoft and then we invested a lot of Time and energy and innovation to make it always high level for You to provide the business continuity and then to provide You with level of performance a lot of built in capabilities In azure are there do management for you and focus on really what Matters for the business. I will name a couple of these like Building high — automated back up. Ability to restore any Database to any point in time in the past. Then disaster recoveries that you can create very easily and Other things. So those core service that’s Exist in azure really help you be more productive. Besides the core services there are other capabilities in azure Like built in intelligence that can reduce, can help you reduce Effort in optimizing effort in security. Some other things like productivity and performance, Examples are ability to scale up, scale down your database and Instances. Use the in memory technology for The most demanding applications and stuff like that. The third pillar on this size azure as of this year allows you To my great your existing application at low cost and that Is actually where managed instance comes into play. Just to illustrate what azure database is, it is a mature Service. Executes millions of queries every year. That is Operated by microsoft. That is the family which new Member is azure database sequence. It is the third Deployment option or third flavor of azure database Compared to the other two which is specific in terms that it Offers you instance level programming interface. To put it very simply, in sql database, when you connect your Application to the database — you are executing contacts in a Single database. Then of course you have Guaranteed level of performance and all of these oughty mat i Can features, manageability, when you connect to managed Instance you actually get — sql server connection point. Very much same as you do running sql and premise. The difference Is that sql is not something that you need to manage, it is Fully managed by. Then you see — that’s the Reason why it is really the best option for modernization. With The low cost. First, it is really close to sql Server when it comes to the supported features. Second, it provides the best possible dco. Now, one step further to click to that Is at the lower level, what are the specifics of Managed instance, what are the 3 pillars of how you can use it to Achieve easy migration and modernization of your Application. There are 4 different things That we want to emphasize during this presentation and we will Show all of them. First one is actually sql server Compatibility. What does it mean? it means sql server is a mature Product, 20 years around, a lot of features inside and then if You compare azure could prior instance in sql server our Developers and our customers are finding gaps. Not all features are supported. Managed instance significantly Reduces that gap. There are a lot of features Coming out of box in managed instance. What does it mean for You? if you want to migrate in modernize application it means That most likely you will need to repoint your application from The on premise to managed instance it will work without Any change zero development cost so you can focus on Modernization. If you are developing new Applications you really want to use the full programability Stack of sql, you need things like clr, cross database Transactions you want to use link server all of these things And managed instances. Now the choice for the new Application between sql database and managed instance is really In terms of how reach is the feature set that you want to use In the database layer. The second aspect here that i Already emphasized, managed instance is part of sql database Which means all of those sql it is managed and it is not Infrastructure as a serve. It is not a vm that you get Automatically provisioned for you, it is highly a available That is operated and managed by microsoft. All databases and features that You can find in the rest of the sql database are already there In managed instance or will come as part of the managed instance. Managed instance as of the beginning of march is in public Preview. We are working hard to make it available generally Available for everybody. And then as part of the journey we Are adding a couple of missing features and improving the Stability and quality of the product. The third pillar of managed instance is very, very unique to It. And it is about security. Basically managed instance is a Service that is running fully contained in your network which Means that alternate working communication that exists there Are under your control. You see them. You can control them and Block if you don’t like. To put it very simply, managed Instance is a case a base service that is accessible over Private ip not public. With managed instance if you have Need to build application with the highest possible level of Security, if you need to meet strict security demand of your Company or company for which you are developing, then you will Definitely consider managed instance because of the virtual Network integrate. And of course it is there to Enable some very interesting scenarios like hybrid scenarios. You have your instances of sql running on premise. You want to Off load a couple of portions of these in the cloud you want to Keep the connectivity toe the private channel. This is something that you can achieve through managed instance Because of this integration. The fourth thing is actually About business model. I’ll talk about this but the main thing Here is it is very easy and intuitive — what are the input You need to provide to create managed input. What are the Instances you can scale up and down and where are the resources That you pay for? okay, now let’s deep dive into all of These areas. So the goal of Managed instances is to keep the compatibility with never us Version of sql start from 2005 and up. As i mentioned basically the goal is to eliminate any changes And help you use the tools and the drivers and to keep coding Practices that you have on sql server on premise. They stay with managed instance because of the highest come Patability. At least here couple of most important Features available out of the box starting with native restore. It is very unique with managedden stance you can take Your database created and just restore in managed instance with A single so that way you can basically Have a copy of your system which is exact 100 same in your Development environment and on premise environment and then That way you can migrate a huge portion — a huge amount of Data. Hundreds of gigabytes and tara bites. Then for the developers the things that they are interested In the most cross database queries and transactions are Available. If your transaction needs to use multiple cases that Is often the case. Very rarely a single user database, then you Need to have some easy methods to query across or to run Transactions across these databases. Same way as you would do that on premise you can do that with a managed inthis is. You can create multiple case a bases and query across. A lot of features i am here emphasizes security. Sql server Is the most secure database in the world and then we tend to Keep that and augment that in azure further. So all of these Great security features that are important for your application And for the compliance are starting from en scripting Address. Sql audit which helps you what are the changes in the Database and then always encrypted which helps you Actually to have data encrypted in transit between your Application and the database and data Masking on on and so on. Features that are highly and Frequently used in sql database a part of managed instance Starting with sql agent. You can create different types of Jobs. You can orchestrate any Processing with the sql agent very easily. You can have Existing jobs that you perhaps developed on premise to the Managed instance and continue using them as you did. Database mail for any kind of notification is also there. Now, feature that’s we call scenario enablers which means Very specifically used database features for certain customer Scenario we selected a couple of these and made them available in Managed instance starting from changes to capture for data Housing an lit tick types of workload. Notification between the Database and application tiers. Basically very efficient data Communication. And then transaction replication For various scenarios including nces. Migrating from one environment to another and common language Run time. Clr or common language run time Is known in sql which allows you to write code, deploy in the Engine and run them in sql. That way you have typed Connection between your code and your data. And also it Simplifies some deployment models that you can use to Preserve the knowledge and the investments that you are Developing crew have. Now, let’s talk about some Specific services. Sql server is very rich product. It includes several services. Managed instance doesn’t include All of these services. Business intelligent services Are not part of managed instance. Managed instance is database engine run as a service in the cloud. What does it mean if you currently use or you plan to use Vi services what are the services for you? luckily or The integration they are platform counterparts ins azure Which you can run integration services in avf v 2 run time. The great news is that you can integrate these services very, Very easily. Very easily. For the reporting Purposes, of course, our strong Recommendation is use rbi in your reporting service that we Have. If you want to keep reporting Service and if you want to use reporting services still, for Now the only option is to keep reporting services within the Virtual machine connected to the managed instance use it as a Data source. This is actually high this Modernization will look if you have multiple services along With a managed instance. More specifically for these Integration services, it’s a very nice story because when you Design the solution in cloud you can independently create your Integration services environment and manage the instant Environment. You can provision very very Easily to azure or rest api or.Net. They have nettive Integration. So when you have your packages developing for Ssis you can deploy those packaged in manage the instance. The database part is automatically managed. You can use agent to schedule the job execution. What happens Ssis service from the ssis run time. Then of course reviewing results and seeing the status of the Execution is, again, there and incorporated. So this presentation contains some useful link you can use More to explore about integration services in the Cloud and the way how you can integrate with a managed Instance. The great thing managed instance And ssi are there to give you a lot of existing development Opportunities, but also to provide you full solution. So The great thing is not only that you can use microsoft component, You can also use third party component and third party to run Within the ssis which means you can further extend as a Developer you can develop the ssis by developing a custom Code. Now, the next important point is That managed instances also integrated with azure services. If you think about migration of the database, if that is the Main case because of the modernization, then you don’t Need to do that manually. You don’t need to script out the Procedure for migrating database is and switching the application From one premises to the cloud. You can use azure immigration Service. How many have heard about it? Okay. Large number of people. Basically data immigration Services is there to help you with the easy and seamless Migration at scale and also includes the minimal down time Option. What does it mean? It encapsulates all of the Migration regardless of which source and migration you are Using. With minimal down time you can control the point in Time when you run your application — when you stop Running the application in one environment on premises or Virtual machine and you start running that application against The database that is in managed instance. With the dms it is possible to achieve — it will be possible To achieve really minimal down time less than a few minutes. So before we go to the next section maybe we can take a few Questions. Yeah?>>actually that is on my next Slide. You>>does dms have size limitations?>>If you think of it as the destination environment it has Limitation today when you per perpreview 8 tara bites. So the question is does managed instance in memory tables? The answer is yes. There are 2 service tiers that are Containing that support. Let me do the following. I Believe many of the questions you might have are already Covered. Then i will go and we will have at least 10 minutes For the q&a. So let me quickly scenarios These capabilities that are there in the managed instance. They will help you basically run the highly available and Scalable application. When you start and you see that In the demo it is easy to create new managed instance to drop and Resize the instance. It is a few clicks of azure or few line Of power shop. By incorporating and controlling The life time is easy. What you get free definitely is All patches and all operates free of charge for you. It is taken care of by microsoft and you just get the most Secure, the most stable version pretty much every month. That includes operating system and sql server patches and Upgrades. I mentioned you have multi back Ups. So the system is such that you just control how long you Want to keep your back ups. It can be 7 days, 2 weeks, 3 Weeks, a month or something. And then basically system is Taking care that all of the back ups are there so any database at A database level you can go and restore back using the very Simple mechanisms. Now, That means that it is running on availability behind The scenes. So you click to create managed instance. We Provision highly available cluster for you. Basically if it goes down the secondary automatically takes Over your application. Practically you don’t notice the Down time. That is the thing. Basically if you compare — if you think about how this Increases the productivity, you Just try to create or configure always on availability group and You see how that easy is. Same way across the region. So Building high level gives you high availability in the region. Across the region basically you can have disaster recovery Solution based geo replication. It is a matter of a few clicks Or api calls from the power shop. You have your primary managed in one instance. You create Managed instance in another region. With a few clicks you Establish the replication link that’s all. So always on application is happening behind the scenes. Then you can control whether you want to — in case of a region Failure you can choose whether you want to manually fail over Or you can let system automatically fail over. You have some knobs to control. That is like super easy and, Again, productivity boost. Of course, another pattern for You is with this you can create globally distributed Application. Sql database and managed Instance will follow that availability. It is available Around 40 regions in the world. Imagine if you want to have Globally distributed application or if your customer has that Demand, you can actually achieve that only with azure sql base Procedure. The same architecture and Managed instance inherits all of the security compliance. So Basically it means that your database platform is also Compliant with i think around 40 different standards and that Gives you a lot of — basically that reduces your effort to make The platform compliant. And then i just named a few more Important services like detection. You can configure it For your instance and then the detection system will detect any Malicious attack like dos or sql injection and report to you with Actionable insights what you can do about it to protect your Database. That is 24/7 protection for your database. Under roadmap ability to monitor, trouble shot and tune Your work loads running in the database. What we call Automatic tune first degree coming to database. Basically query plan, automatic tuning is already available. I Am referring to index recommendation. That will be Also available in managed instance. Basically a lot of build in capabilities coming there to Just focus on the business to manage the database. Now, let’s talk about the virtual network integration and Security. So this is more explanation to what i already Mentioned is that your instances are deployed and connected to Your virtual network at the next working level. That basically means they are fully contained and the traffic That is going from your network into your network is fully under Your control. Basically you can apply Different network security rules to protect your end point. You can control precisely who is connecting and how. Today managed instance that doesn’t have public point Enabled which means if i deploy — if you deploy managed Instance and if you just create a couple of databases there or Deploy your application, nobody will be able to even connect to That. You need to take extra step to Enable the connectivity. Public end point is coming as Optional. Mainly it will be there for easy Testing and, you know, q&a and development things. Basically the feedback we are get from customers they like Very much the fact that it is isolated, that it is protected At the networking level. As i already mentioned both Scenarios when you have your application in the cloud or your Application and your own premise those applications will talk to Managed instance through a private channel. That is Extremely unique. If you think about multi layer application You can easily open up a front end to the internet and then Your database is in the back end to your application and not Others. Now, i will now spend some time Talking about what i call developer perspective which is Actually what you need to know when you start working with Managed instance, what are the important information. So you definitely need to use latest drivers that we have for Sql server of any kind because managed instance is actually it Is a new member of the family. It has a way to uniquely Identify itself so all drivers need to know that they are Talking to managed instance and not to something else. Then also when you connect to managed instance, as i already Mentioned, it is interesting when you test your application To embrace the fact that it is running inside a virtual Network. So you definitely need to have Connectively precisely controlled in this managed Instance. This is comparable to sql is running. Fire wall is on And you have a hard time to connect to sql it is protected. The same way with managed instance. It is really Protected use. When you think about it in your Testing and deployment scenarios. Public end point is coming. So you will be able to turn it On an then control the access from the public internet. Managed instance platform is a service which means there is a High availability built in. But there can be some Transient errors behind the scene. You Can use the latest drivers and you can use some parameters to Control how much your application is resilient To this temporary fail. So basically what does it do for you? it tries the retry logic. If the request fails the application will repeat the Request. From the user point of view it Will be a query that was executed a second longer or 2 Seconds longer. No down time. No crash, no issue for Applications. The connectivity resilience is Extremely important. Feel free to use the tools that You are familiar with like managed studio definitely so you Can go and manage in studio is really adjusted to managed Instance and it works with managed instance and properly Runs. You can also visual studio plugs In to deploy the schema and sync between and stuff like that. So All great things about deploying schema from the development to Production and test environment is there. Now, another thing that you should know about managed Instance as a developer is that it is really running the latest, Greatest and most stable version of sql. What does it mean? it Means that — it is newer than what is commercially available On premise. Today is 17. Managed instance is newer than 17. It is something that you will See on premise a few months from now or a year from now or 18 Months from now. The way we run the database Services it is very unique. We are called first company. Everything we develop for sql we are deploying first. So we built strong mechanisms to protect our 5 million databases From being — from being interrupted or impacted by the New bits. So basically practically every Month we are released new sequel engine version and existing Application to cloud you don’t see that as an issue. What is the key catch here is that when you run your Application you should be — he should stick not to the sql Engine but the database compatibility level. Database Compatibility defines how engine will work and how features are Introduced in sql. And then it also affects the execution plans And other things. But here is the illustration. Managed instance azure sql base is the latest sql. It allows to you use compatibility levels from 100 to 140. 100 Is the same as you would be Running sql server 2008. So basically the latest sql you Have behavior of sql server 23008. That is a great thing. And then when you test and develop your application against The database compatibility it doesn’t matter if run the Previous or latest version of sql, but that gives you some Additional advantages. You are exposed to the really Cutting edge technology that you produce which means you are Running your application on 100. For legacy features your managed Instance behaves as 2008. You have ability to improve and Modernize your application by taking new features. A couple of examples temporal and jason all of these new Features are there and you can start immediately using. Compare that with running your application on 2008. Unless you go to the latest sql which is happening not that Often you cannot use and modernize your application. This is really great capability. Now, managed instance definitely With a set of features really behaving as sql on premise. If You need for any reason to distinguish and inform your Application that is running against managed en stance the Engine 8 that is the condition. That is the instance identified Itself. Then as a developer, you should Be aware of a couple of temporary limitations that we Will remove very soon. One of them is current and public view. There is no way for to you say want to run it in the east u.S. Or in any region or any time zone unfortunately. But that is coming. In the meantime if you are Starting developing in managed instance you can use built in x Time zone function to convert to any time zone. That is time zone function owners the daylight saving Changes and all of those things that are coming as parts of the Updated roll out. When you start using a time Zone, you don’t care any more about that. Now, as i said, ability for to you specify time zone at the Instance level it is coming. It is not here. The second thing you should be aware of when you develop Against managed instance is that currently instance collision is Fixed which means we do not allow to you specify instance Level. What does it affect? Meta data and it affects 10 db. Basically if your application is Heavily using queries with 10 db creating temporary objects and Joining between the persistent objects then you might Experience the conflicts. So the current work around is During the development process put the resolution directly in The code and as i said, we are working on improvement which Will allow you to during the instance creation to specify i Want all of the co-lations for databases to be in a certain Callation. It reflects the same behavior as on premises. I’ll just roll this slide. Just a second. This is about a database compatibility certification. This is expansion of our suggestion. Test your Application for a database comfort level not the exact version. We are running some program that includes isv and basically we Are changing the approach and helping different isvs and Partners to embrace this database compatibility approach. What is essentially it is about, it is the process for any isv or Any developer who wants to start a managed instance and maybe High great to managed en stance. Before going to managed instance You run the tools we have diet a base migration assistant. That tool will perform the detailed assessments of your Code and inform you if you have any breaking change, anything That will not work if you run it on managed instance. If your tool is clean, then basically you can just say, hey, For this comfort level my code is running safely. I am going To deploy and run without any concern. And of course testing is always necessary. Right? but not to The extent of testing migration from one version to completely another. So it is really some basic testing. The process itself is there to reduce this effort that Everybody needs to invest and move to managed instances. Then at the same time microsoft actually will be working and Making sure that if you have any issue with this approach, we Will fix it with the highest urgency. I will remind you we are running This service with more than 4 million databases. If if we introduced any significant regression or Problem for existing problems, we would be out of business definitely. So basically, first of all, we are doing all necessary testing Work in-house to make sure this approach is working. The story for isvs and any other developer is just stick to the Comfort level that you think is optimal for you and then go to Managed instance without any problems. And of course people are asking okay, managed instance close to Sql server almost everything is there. What is missing? Is there any small print thing? this slide is about it. Not all Of the features are natively supported there. The majority Of the features we didn’t support there is no need. We Don’t see the need. If you think about creating all Of these availability groups, no need as i explained we do that For you. No need forehigh level Availability and disaster recovery. There are other Features available that you can use. It is basically like native in those Authentication is not supported. Azure is everything Should be exploring. It is the identity of identity services. So basically still you can thanks to the sync aiding Single sign on. You can log into the managed Instance using the credential and that’s supported. Then some features like database mirroring is definitely not Necessary because of the ha and replication. Now procedures like how many of you have deployed extended Procedures that you developed in sql? okay, cool. So basically that’s great. We said for a long time that People should be using slr. Extended Procedures we didn’t go there enabling them. It was the right choice. There is a list of features that we know that people are using. We know that. But basically implementing those Features just requires some time. And given that there is a service and the ga do not stop Developing and improving service constantly. Some of these Features are on the list, the biggest ones are the fast table. We still don’t support it. If you have strong need and you Cannot replace that with binary on any other alternative, then Sql and premises or virtual machine is the option. And then cross database distributed transactions across Multiple instances or across heterogenis providers. So that is a complex scenario. Definitely we want to tackle That one. But it is not coming in the next 4 to 6 months. Right? so if your application has strong dependency and always Uses it to run the cross instance transactions, then Still managed instance is not good option. Cific for certain scenarios. Search Database they are yet to be implemented. The list is not too long and on One of the previous slides you can find the full comparison Between what is available in sql and what is available in managed Instance. The good thing i mentioned some other things will Come very soon. Then the last thing that you Should know if you use managed instance is that definitely There is opportunity for you to modernize your bi analytical Solution by embracing other services that are integrated in Managed instance. Power vi. There are some other interesting Capabilities that you can leverage here once you are on managed instance. One of the interesting is you can actually have your ability To your read only queries to read only replicas. As i mentioned managed instance has one of the service tiers in Managed instance has multiple replicas. One is available for Read only. If you specify read only application intent, the Query will be rerouted to this secondary replica. Basically that allows you to have doubled benefit and number Of transaction that’s you can run for read only free of Charge. Also you can use the same Capability if you have –>>how many secondaries?>>Secondaries just one. One local secondary. But the same capability if you have godr. Then secondary side you can use for the read only work loads. It is also interesting if you have one actsive and multiple — One active and multiple slaves distributed around the globe so You can have one central that is constantly being invaded and Data being pushed to the regions. Then you have read only reporting running in the regions Excellent for having close to customer database running in the Solution. Then like another thing to have In mind you can built in your instance life cycle in your code And you can size your instance resources appropriately to your Needs. What does it mean? you can actually start — you Can run from your code in power shell around the code that is Dynamically created or drop instance when you don’t need it. Or resize instance. For instance, there is a Scenario when people over the weekend they don’t need to Run — there is no workload. It can scale it down. During the Working days you can scale it up and then basically that’s a Cloudy con mow thing. You can run your workload most Optimal. That is something you cannot do running the virtual Machines or on premises solutions. Of course, whatever you do focus On your application and the platform will do the rest for You. Now let’s show the demo. Let’s See the managed i object stance instance in Action. I need a few seconds ond toconnect to prepare that for You. Okay. What you see here is azure portal. I created a couple of resources For this demo. The resources include one Prepared and managed instance. Storage account that we will use For the database immigration. Virtual machine that is used for It purposes to have secure connectivity to your managed Instances and also to mimic the source sql server. You will see some others. Let’s first see how — what does It mean to create managed instance. How i can create managed instance. So basically managed instance you can find all in resources. You can just click and say, hey, i want to create one of my Managed instance and let me do something. I’ll just take a couple of parameters not to invent — so There is a name and demo, user, I will intentionally use this password because it will be Easier for me later on to connect. And save time. You create a password. This is a sys admin password. You can specify the group. I will use this one for a specific reason. Then the region. So it isal owe kited in the region. You specify the region for this session. You have all available regions Here. Then very specific thing is you Need to specify virtual network. It needs to be pre-created where You want to place your managed instance. Right? so how many of you are Familiar with virtual networks? great. So you know what i am talking About. So the subject needs to be dedicated. No resources inside of that subject. Luckily you can partition your virtual network to have multiple Subjects so you can create. I will specify this and let me Show you the new business model. So there are a few things that You can select in service tier. One is the generation. It is available gen 4. They are available publicly. Then you can specify how many cores and how much of the Storage space you want to have using these sliders. This calculates the cost for you. That is a monthly cost. So depending on the service Tier, i’ll explain that later. There are 2ty er. General purpose is using azure premier. Business critical is using this. So one of the differentiation points between those 2 is Actually azure performance. There are others. With the storage you say how much of the storage i need for This instance? what is the size of the disk That i am going provision? then it is interesting if you have Your license on premise with the license mobility you can say Hey, i have license. What does it mean? It means that you can trade your license on premises for getting A discounted price from cloud up to 30 or even more percentage Which is really significant what is great here during the 6 Months you have dual rights for using this license. You can use It both on premises and the cloud. This 6 months is a period for you to perform immigration. This actually significantly ost. Both stand and enterprise with license mobility. Now, standard will a lee to you go only to take general purpose Areas. Enterprise allows you to buy Both. I’ll have a slide. It’s contained in this presentation. So you will see it. Then here is the thing. I just say, click, create, pin To the dashboard that’s all. I hope it is good. I issue creation. Hopefully after — it validates My inputs. It should be a few minutes, 2 Minutes you have your instance running. Memory is something you cannot choose with the current version. Depending on the integration several gigabytes and 6 Gigabytes in gen 5. Specifications are available in The documentation. So while it is running actually I wanted to show you the structure of the demo. So as you can see on this screen what we have here we have on Huge virtual network. We have sub net dedicated where We have one and we will deploy another one. We have virtual machine that is Actually sitting inside of the same virtual network which means It’s enabled to access this. This virtual machine sitting in The same private network managed this instance. The results of dms deployed in this. I’m creating from the portal. Yes. Then i also do a few other things. I will show you how you can take your simple application and Migrate your databases to back up restore and run your Application in the cloud. Then the third thing is i’m Going to run the dms migration and show you high you can easily Migrate and scale using the highly available service in the Cloud. What is important here azure Storage that is deployed is used as a connectivity point between Achine. In order to be able to restore In managed en stance that back up needs to be placed under Remote storage. This is the structure of my demo. I hopefully — sew my deployment succeeded in 2 minutes. This is great. I have my instance up and Running. My 8 course instance with more Than one tara bite is running in the cloud in 2 minutes. That is really awesome. What i wanted to show you here Is that this is my vm. I logged into this vm. I logged in because it has public end point. From this vm i can connect to my Managed instance. Also i can migrate application a Simple application running on this virtual machine. Let me run the application to show you what it is. It is application that is currently connected to my sequel And premises and my demo vm. And if i run it, it will start doing something, showing some Results like on line transaction report. It is a very ugly application. It is a leggy application that i don’t have source code for it. I have no choice rather than just hold it. It will run on managedden stance. Sorry?>>Read only or also writing?>>this application is read only. It doesn’t matter. I will show the code behind the Scenes. This application is running and That’s fine. I can pause it. Take the backups of the database databases and restore it again. Restore it and run application again. What i’m doing now actually i run this script which is a Template script. What i am doing here is creating Credential that both my sql on the vm and my managed instance Will use toe safely connect to the storage because there is a Connection point. It deploys back up. It pulls back ups from azure storage. To run this i 2 parameters the url and the sas key. I won’t go into the details you go to the portal. You click on the storage account. You create the sas key then when you have the sas key you need Two parameters the url. I will run this template. I will just replace this and i will specify the Sas key. Let me see. This script is running on virtual machine. So on premise sql is able to reach to cloud. I also change connection and run it against this managed instance That i had created. Again, create sas key there. I performed the first step. The second step would be hey, I’ll create — i will back up all of my databases. Just make sure that i am running this on the virtual machine. I will back up all of my database is to azure storage. That should be fast. Sorry. Again this is a template script i will do in order to preserve The template. I will just create a new file>>Is this azure file share?>>it is actually not file Storage it is azure block storage. This is the guy that i’m using. I created storage here in a Certain region and the only thing i need to know is its urs And saas key. When i run this script against Sql what it is going to do, it will just back up all databases. A couple of databases to this storage account. And next step is to restore these Databases on managed instance. I will create template script. It is using template because i didn’t want to — i didn’t want Hard code any parameter. By the way, this is also used by The lab tomorrow. If you are interested you can Come tomorrow to my lab and it will be two session, 75 minutes. Soul be able to do various things, created managed Instances to play with this in more details. I will need to make sure that i am doing this againsted managed instance. My managed instance you can see it has 0 database S. I run the script to restore the Database is. Unique, extremely unique to Managed instances restore capability. It will take some time to Restore. It still takes more time because The databases are being assigned to higher level group Automatically. Your instance is highly Available because of any instance it will have a spare Replica. While it is executing let me Execute one of the scripts i have here. This is a script i call typically managed instance, Introduce yourself. So there are a couple of built In functions that we create that are specific doctor we just Created over rides for managed instance. Those are well known functions, server name and either. You see server name is a fully connectable name the short Instance name and then the fully qualified dns name for the Managed instance. What managed instance says it is Microsoft azure the verse like the rest It has addition 8. You know you are working with Managed instance. This microsoft major version Tells you that it is running version 15 so we can calculate 13 Is 22014. This is even newer. You can use similar script to Code it against — to use the meta data and build in the logic Within your code. It will probably take a minute Or two to restore this database in managed instance. So while it is working let me use a few minutes to show you What the options available out of the box. So the instance that we created. First overview you have very Basic information about the region, the sub net. Subscription and other things. You can easily get the Connections in all of these drivers. You can copy them from the portal. There are some interesting things. Basically a person who has azure permissions can do that. Then you can set up the azure authentication. What is also very interesting you can just say hey, my managed Instance needs to be bigger. Let me change the storage and Apply and we will see how long it will take to actually change This. By the way while this is being Executed, this instance is available for your application. There is only — happens to the Newly created instance. During the process a few Minutes, application doesn’t see the problems. So i restore my database is. As you can see they are all here. 3 Databases. As i said by default i kept the Original come part built level i can later decide to increase The comfort level. That is up to me as a user. Then so let me quickly run this — my application. I will change and say hey you need to use this new instance in The databases. I will resume. It says.Net framework is not enabled. It doesn’t mean that it is not available. It just means it is not by default en veiled. We will just enable it in a second. So i can go and connect to my managed instance and basically Do these sp configures. Just know that sp configure is Available for you so you can play with it. Why is that so? loyed You have a couple of functions. So this application is Leveraging this. I enable clr and basically my Application is running against managed instance without any Change. Now what is also beautiful if i Here. Let me use the password because I always forget and i cannot type it. So i can use profiler, connect To my managed instance to see actually — i can filter by Application name, not organize but filters. And then i run profiler it is interesting. You see it actually goes and says those are the features. Get sp transaction get country by transaction. I can go to these procedures and i can go to these procedures low Kited in this database and let me show you this one. This one is actually using clr and this one is using cross Database query multiple databases. It works out of the box. This one is using another feature that is really unique to The instance the global temp tables not the local one the Global one that exist until there is a connectivity. So very common. So basically i can go further. I could create link server and change my application so one Database on premises and 2 database in the cloud. It works because link server works. This is really beautiful. I will stop here because we are approaching the end of this Session. The last thing that i want to Show those guys is about to complete. It typically uses 4 to 5 minutes minutes. But as last step actually i can show one — another — the last Thing is — yes, managed instance comes with instance Agent that is highly available in automatically deployed. So i can quickly script and it will cry ate the job. An run it. This job is doing some table Rebuild and stuff like that. I can further go and configure The database notification or whatever. So basically as you can see Here, the full spec is available and that really is a guarantee For you that any application you have or any development Patterns you have is something you can Easily support. We didn’t have time to go to this. It is in the session. It is in the slide deck. I just wanted to show the list of resources that you can Explore further about the i invite to you come tomorrow. There are 2 session was a lot of opportunity to play with managed Instance yourself and learn about it. So thank you very much. [Applause]>>one of the early slides Mentioned sql [inaudible]>>That is a good catch. Basically we do support direct Migration and database restore from 2005. The database comfort level 100 Is the lowest one. What stores when you restore 2005, You get 100 comfort level with the same behavior with sql And saturday, sport it in sql any more.>>, Very the link to any server destination running on premises Or in the cloud is possible. What is not yet available is Link server to oracle. But we have it on the road map. Basically in any environment for the cloud, hybrid you can run Link server queries. Not yet. It is not yet supported. It is on the road map. It is definitely not for 6 months. It is a little bit longer Roadmap.>>When will the preview go?>>You question the lady had?>>not the ga. The preview hasn’t been accepted. If we want subscriptions we have to accept it.>>So here is the thing. If you want to test it is just Another of prioritization. It will take us maybe 2, 3 Months to open it fully. Feel free to reach out to me directly. Do not hesitate. Send me an e-mail with the Details. That is fine. For everybody who actually wants to use managed instance the Preview is still controlled. Just if you plan to start Immediately use my contact from the presentation and we will make it for you.>>Thank you.>>Notification service is Actually supported. Service broker and notification Services are supported, yeah. Which actually allows very interesting application Patterns.>>For migration purposes what Do you have to use? migrate a large database.>>It is one of the options. Another one would be transaction Replication indirectly or directly is not supported. Not yet. So we are considering.

Leave a Reply

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