Uncategorized

>> Hi and welcome to another episode of Data Exposed I’m your host Jeroen ter Heerdt, and today, I’m joined by my colleague, Mine. Hi Mine >> Hi >> How are you? >> Good. Thank you. How are you? >> I’m doing good. So what do you do at Microsoft? >> Yeah, I’m a Program Manager in Azure Data team, and I’m focusing on SQL Server on Azure Virtual Machines >> Cool. What are we going to talk about today? >> We will talk about first of all how to position SQL Virtual Machines for lift and shift migrations, and also the new features and benefits of SQL VM resource provider >> Oh exciting. Cool. So tell us all about it >> Okay. SQL Virtual Machines is part of Azure SQL together with managed instance and single databases >> Yes >> Managed instance and databases are part of the managed platform where the high availability, disaster recovery, backup configuration comes pre-configured for the instance from the resource when customer creates provisions and resource from portal or APIs Also, it enables the intelligent security and performance features that are specific to Cloud >> Okay >> But SQL Virtual Machines comes into picture where customers needs bonds to control and manageability level For example, they can choose which version and addition of SQL Server they want to run, and they can choose to control the update and pitching policies on cycles while at the same time they can use Azure backup services or our new HADR configuration services to automate the manageability and administration of SQL Server SQL Virtual Machines offers control and access on all levels, on SQL Server configuration level, operating system, VM, and also the underlying architecture Like for on legacy On-premises systems, customers might be running a Failover Cluster instance for high availability with the shared storage >> Right >> They may need to use it on Azure because, for example, they may need to keep the simple recovery model So this is possible in SQL VM environment because they get access to the storage They can configure storage according to their preference >> Right. They control everything, right? >> Exactly. The whole architecture including the whole infrastructure VM, VM size, operating system either Linux or Windows, SQL Server version, in addition service support 2005 and above Also networking and architectural SQL Server for HADR and how it is connected with the rest of the business CRM web tier and rest of the architectural platform >> Okay. Cool >> Yeah. We recommend SQL Virtual Machines if customers needs to access all of the underlying levels, and they want to control the manageability they desire >> Right. Because if you choose anything else, the managed instance or the Database as a Service, the single database, you lose a bit of that control, so there’s less flexibility >> Yeah. You get the full managed platform, and there is a lot of benefits So it maximize your return on investment while you need to lose control on at some levels >> Yes >> Because it’s managed by Microsoft Yeah, if you want to keep that control, then we have an offer so you can get the same level on performance and availability by keeping the control >> Okay >> Yeah, with virtual machines all time >> So it’s a trade-off to be made >> Exactly >> Okay >> So with this context, we made a lot of investments for SQL Virtual Machines, and we created a new management service, and we are calling it as SQL Virtual Machine resource provider This is a bit of a technical term It’s actually referring to a new control plane application available on Azure data platforms It’s a Microsoft.SqlVirtualMachines namespace, and we are modeling SQL instances running specifically on Azure Virtual Machines with this new namespace and new services >> Okay >> We’re modeling the stand-alone SQL Virtual Machine and also a SQL Virtual Machine group that will participate in an high-availability configuration and also on all these high-availability groups >> So why did we introduce this? I mean wasn’t life good already? >> Yeah, exactly a good question Yeah. Life was good for some SQL VM customers and was not perfect for some of them Because there is multiple ways to deploy a virtual machine on Azure or running SQL So they can choose to use Microsoft SQL installation

and use an SQL Marketplace image to deploy the Virtual Machine So if they are doing this, then they get all the benefits and they get manageability and integration with Azure Data Platform But if they are choosing either bringing their own VHD or using an operating system only image from Azure Marketplace and start installing SQL Server, then they are not getting anything about SQL Server manageability or administration >> That isn’t the case that you take like a Windows or Linux image from the marketplace or upload on VHD? >> Exactly >> And then install Linux with SQL Server >> Yes. Exactly >> Okay >> Yeah >> Cool >> So in this case, customers will get services offered by computing So they will get Virtual Machines services, very generic services and they will not get anything about SQL because we don’t know which VMs are running SQL The VM isn’t their, subscription, we don’t have any access and we cannot offer any SQL services With SQL Virtual Machine resource provider though, now they can register to the resource provider by linking their existing VM resource to a new SQL Virtual Machine resource, and then they get integrated into Azure Data Platform, and this unlocks all the manageability available for SQL Virtual Machines on Azure So the comprehensive feature set is the benefit for customers because now they can automate pitching on SQL Server They can automate high availability and disaster recovery configurations and simplify it They can view their SQL Virtual Machines in a centralized and unified dashboard together with Azure databases and managed instances >> Then it doesn’t really matter if I chose the VM in the end >> Yes >> I mean all the managed services as well, all of them are then in one pane >> Exactly. You become part of Azure SQL family and virtual machines is just the deployment time of your workload, and you can change it anytime >> Cool. Okay >> Yeah. This is a huge benefit Instead of simply having an infrastructure for your SQL workload and not differentiating SQL from any other type of virtual machine workload This is a huge benefit for our customers, and there’s no additional charge with registering with SQL VM So simple license conversions is another thing >> Okay >> It’s a huge simplification with SQL VM Resource Provider because the license of SQL Server is hard-coded in the image if they are using a SQL image from Azure Marketplace It is either a pay-as-you-go SQL VM or a bring their own license SQL VM, and changing it is not possible >> Okay >> Was not >> Was not >> During the life cycle of VM Yeah. So they need to recreate the VM >> Okay >> But now with SQL VM Resource Provider, a license type is the property of a resource and we can dynamically change it >> Okay. So now it’s possible to switch from >> Exactly >> Okay. From one to the other >> This is enabling huge cost savings for customers, either to convert from bring your own license to a pay-as-you-go, because if they don’t need the VM running 24-7 all the time, then they can switch the pay-as-you-go licensing and only pay for the seconds they need the VM operating >> Right. Exactly >> On the other hand, if they already have licenses of SQL Server and active software assurance for many reasons, they can convert to pay-as-you-go VM to use the existing licenses on the reduced Azure bill So it has benefits to multiple scenarios >> You can only get that when you are just with this new RP? >> Exactly >> This new [inaudible] provider Okay. Otherwise, we don’t know what’s happening inside the VM >> Exactly >> Okay. So what do I need to do as a customer is this? What do I follow? >> I will talk about it then and then I will demo it, but I want to first emphasize the compliance problem we are solving basically on resource provider as well >> Okay. Sure >> As I said, there are two type of licensing methods available So either on the customers paying SQL Server license as part of monthly Azure bill, this is pay-as-you-go model, or they are using Azure Hybrid Benefit, which is saying customers only have enough course of SQL Server licenses protected by software assurance, and software assurance gives them the license mobility rights, so they can use them to install SQL Server on Azure Virtual Machines According to Microsoft product terms, customers using Azure Hybrid Benefit need to indicate that usage to Microsoft This is for license compliance we need to be able to track Azure Hybrid Benefit usage For Azure SQL Database managed instance elastic pools, this is available by clicking a checkbox on the portal and saying I’m activating AHUB

If they are using SQL Marketplace images, again, on the Azure Portal, they can put the similar checkbox and activate Azure Hybrid Benefit, so that indicating Microsoft But if they are bringing their custom VHD or if they are self-installing SQL and on simply Windows-only or Linux-only Azure Virtual Machine, then they’re not indicating that usage So we don’t know they are using AHUB So this has been a compliance issue, and now with SQL VM Resource provider, they can register and set the license type either as AHUB or they convert it to pay-as-you-go, and indicate Microsoft that usage >> Cool >> So that’s going forward in 2019 After July 1st, we recommend all customers if self-installing SQL Server and Azure Virtual Machine, do this register with SQL VM Resource Provider and ensure license compliance and unlock all the comprehensive feature set for SQL VM >> Okay. If I deploy after 1st of July, we need to >> Yeah >> As a customer I’m advised to do this, right? >> Exactly. For license compliance we advise to do that and how do you do that. Yeah >> Yes, that’s what I was looking for >> Exactly. Because this is a new resource provider for all new resource provider, it’s subscription needs to register with a resource provider It’s a one-time operation and needed on the subscription level They can do it through Azure CLI with the command seen on the screen below eval, or they can do it through a portal >> Okay >> Once the subscription is registered, then they need to run in Azure CLI or PowerShell command for each VM running a SQL instance That command is very simple so they will be simply saying, create a SQL Virtual Machine resource for my existing VM by pasting the name resource group and location of the VM and setting the license type License type is the must-have property here They need to tell us what type of license they are using. Either- >> Pay-as-you-go or AHUB >> Here, the AHUB is a constant they are giving us, that they have enough licenses and active software assurance so that they are eligible to use their right on Azure So this is very important for compliance Once they run the command, to get the manageability available through SQL VM Resource Provider, we need to have an agent on the VM to deliver the features on the virtual machine level This is called SQL IaaS Extension It has been on the market a long time >> Okay >> So if the VM owner, they had the agents running on the VM, then once they run this command, they will be registered in full manageability mode and they will get access to all the features >> Cool >> But if the agent doesn’t exist on the VM, then we will register them in the lightweight mode >> Okay >> So what will happen is, SQL VM RP will push a console application on the VM and verify SQL instance existence, and then shutdown itself So it will not actually do anything other than verifying SQL instance existence together with version and addition of the SQL instance So this will register them and it will not restart SQL Server or virtual machine, so it will not leave any footprint on the VM >> Just a quick check >> Just a verification Yeah, there is no availability impact, so there’s no impact Then, it will enable limited functionality So all the flexible licensing and edition updates and compliance will be assured once they registered and integrate that resource into Azure SQL family I will demo soon. After that, they will be able to see those resources in the SQL Virtual Machines builds on portal and APIs, instead of simply being on the Virtual Machine >> Okay >> To unlock all the other benefits, they need to upgrade it from lightweight manageability mode to full mode and they can do it through portal or other APIs as well So once they upgrade the mode, we will download the agents on the VM, and then this is the SQL we start operation SQL Server will be restarted first They can, anytime, restart in the maintenance window and install the agent first, then this will automatically unlock the manageability, or they can upgrade the mode through a portal and then we’ll do it on behalf of them by restarting >> Okay >> So this will assure the full manageability I think at this point, I can show how to do it >> Yes, please >> Yeah, what I’m really talking about This is my Azure Portal, and I have virtual machine’s services here When I go to my virtual machines, first of all, there is no way to filter which virtual machines are running SQL Server, which virtual machines are not running SQL Server >> Right. Because it’s only a VM, we don’t know, right? >> Exactly. So nobody knows Only customers knows

>> Yes >> If they tag it, they give the specific name, done They are maybe a bad for- From the services delivered by a Microsoft perspective, this is only giving them virtual machine generic services So here, I have a VM named as self-installed I deploy this from a Windows Server 2016 datacenter image It actually has SQL Server on it I installed it from my own media It has enterprise SQL Server on it, but I cannot see it from the portal So on the overview, I don’t see anything about SQL, and here on the settings, I get configuration This is just basics, there is nothing about SQL Server But actually it has SQL Server So for this type of situation, what I need to do is open the PowerShell and register this VM with the SQL Virtual Machine Resource Provider It is a one-line command, so simply az SQL VM create, and I need to give the name of the existing VM, and the resource group of the existing VM I want to use my licenses because I have software assurance, so I set the license type as AHUB This is a couple of minutes operation It will create a new resource for them, all types of SQL Virtual Machine They will see all the properties of those resource and the SQL license type as a property in addition to others Now, what happens is, they can go to all services, search for SQL, and now we have SQL Virtual Machines service available on the portal Yeah. This will be the list only the VMs running SQL Server All virtual machines created from SQL Marketplace images will be automatically registered Then they will see all of them here in this field >> Cool >> All the virtual machines they register manually with the command lines, they will be also registered So here, they will see only the SQL VMs and then they can filter and monitor the version edition and license of SQL VM So this is the basic monitoring and filtering for specific to SQL Virtual Machines That’s not the only benefit So once they select the resource now Oops The one I registered was the constant SQL >> Right >> I registered in the default mode, and default mode is the lightweight mode, so I didn’t get any agent on the VM So now when I click “Overview” of this resource, now I can see is the SQL Server 2017, it’s Enterprise SQL Server and this is my VM size I can go back to the Virtual Machine review anytime by clicking on this link and this is my license type, so it’s running a hub >> So we get all of this by just registering it and running this one time investigation on the machine Cool. All right. That’s useful >> You can automate it if you have a thousand of Virtual Machines is totally scriptable on APIs Some are very easy >> I was just been thinking, 10,000, what do you do? >> So you can use the scripting metadata >> That’s the PowerShell of SQL >> Exactly, both of them support it So lightweight mode is mentioned here It only enables addition and license updates because it’s a lightweight mode So by coming here and switching the property of SQL license from a app to Pay As You Go, and clicking on the checkbox, now they can update the license type So think about recreating the VM and provisioning older storage and older architecture This is now a property updates, so there is no impact >> Exactly, because that would be a hassle to do that, right? >> It was a huge overkill. Yeah >> Yeah >> Now actual VM not touching the SQL VM at all It’s just a property of a metadata resource, and we are updating the billing accordingly Either removing the bill because they already have licenses and they give us consent now, or setting the build per second the usage in this part of the Azure build Also another thing to highlight here, the edition change Before, because the billing type or SQL Virtual Machine was hard coded in the image, it included the edition information as well So if a customer provisions SQL VM from an Enterprise 2017 image and they want to downgrade it to standard, they need to redeploy it, because the metered VM is emitting per second while specific to enterprise licensing and to change it because it’s part of the image, we had to redeploy >> Right. That’s a lot of work >> Yeah, and this was also very not good experience, and now it’s changing So they can simply change the edition and come here and update the property, we will update the billing according >> Okay, cool >> This is huge life improvement for the SQL VM licensing

>> Yeah. Amazing >> When they are ready to restart SQL Server and download the image, they can come here and agree to download SQL ES extension and restart SQL Server This will start on template deployment to update the mode of manageability mode of SQL VM resource, it will turn it to full, it will download the agent >> Right. Then I get the agent on the machine and all the benefits that are in the full version and so the lightweight version >> Yeah, exactly >> So that’s easy? It’s just a link at the top and that’s it? >> Exactly >> Wow. That’s cool >> It’s going to take a couple minutes because it’s an asynchronized operation, it will start an ARM template deployment So here is an VM example What happens when they upgrade to full mode? So now in the configuration, they get storage configuration, they can tell us what I/O’s throughput and size requirement for SQL Server, and we will autoconfigure a storage pool for SQL Server Data TempDB on Log Files, and they can come and expand on new drives here So for security we are doing a basic connectivity configuration and also integrating with Azure Key Vault, I mean on behalf of them They can configure automated pushing So for End of Support SQL Server versions, SQL Server 2008 and 2008 R2, all of those deployments are by default configured to auto page for extended security updates in a prefix maintenance window, and they can always change it So by default Sunday is local time 2:00 AM and they can always change it, but all the SQL VMs are configured to automatically enabled for security pitching on Azure Virtual Machines So this is a huge benefit Because on-premises to get security updates, they need to pay a huge cost and in to handle the automation by their self So simply being an Azure Virtual Machine makes it available for free extended security updates, and also it’s available for Pay-As-You-Go licensing So it’s actually an SA benefit but Azure Virtual Machine override it’s benefits, so it’s available for all Azure Virtual Machines independent of the license type and all of them also configured for security features >> Wow >> Yeah, so for backups, also they can enable Automated Backup Service We are configuring SQL Server Managed Backup Service, is a comprehensive pretty good feature, so it supports encryption system databases >> So if I now want to make a backup of the database or I want to configure that, I don’t have to go into the VM and do that all manually, I can just do it here >> Exactly >> Wow >> You can configure it here and manage it here, and if you need more than 30 days of retention period, you can go to Azure Backup Center and configure Enterprise grade Backup Service for Azure SQL Virtual Machine which doesn’t have any retention period, so it’s much simpler So yeah, they get to access all of this, and actually we are investing a lot So we are improving and trying to bring the manageability available our SQL VM up to the similar level of other services So they will soon see many updates on that Also, they can go to Azure Security Center and Configure Azure Threat Protection on Vulnerability Assessment for SQL VM as well So there’s many Azure services integrated and available for that >> So if I wanted to have the threat protection, I need it to be in this full mode and not the lightweight mode? >> You need to be registered >> Okay >> No, you just need to be registered >> Okay >> So this is what I need to say There is a lot of resources available to learn more about SQL VM Resource Provider We have a full list of questions and answers in the Azure Docs But, I mean, I really recommend taking advantage of this new infrastructure and registering, both for compliance and also to get access to the rest of the Azure Data Platform But if anybody has any question or wants to tell us any feedback about this new announcements, please reach us from [email protected] >> So, hey. That’s very interesting. Thanks for sharing >> Thanks for hosting me >> Sure, you’re welcome If you liked this video, please like and subscribe, and I hope to see you next time. Thanks for watching [MUSIC]

You Want To Have Your Favorite Car?

We have a big list of modern & classic cars in both used and new categories.