Hello thank you for coming from this session. My name is Yung Poppy, which I'm program manager and I'm working in Microsoft Azure sequel, managed instance, I'm located in Serbia.
And on this session, I would like to show you what is Azure Sequel managed instance in the show you some tips and tricks that help you if you are planning to go to manage the instant to configure it or to monitor troubleshoot some issues on managed.
So today is agenda, I will have I will show you shortly? What is managed instance?
Oh, so you want the different pricing tiers how to choose between business critical general purpose. Hyper scale that is coming soon. Then I will show you how to what are some best practices for configuring managed instance?
How to migrate from your on premises database or Azure or SQL server VM 2 managed instance and show you some recommended management tools that can help you while you're working on management.
So let's start with this introduction.
Now the first question is why would somebody use managed instance the reason is past capabilities.
Manage instances SQL server that you're using but it is just configured and managed by Microsoft in Azure team, so most of the maintaining stars like point in time is store scalar scaleup scaledown for escalates everything is built in.
This into a marriage instance.
So just imagine that somebody just took all this basic administration tasks that must be done in every SQL server, and just implemented somewhere and tell you OK now you can just provision it and use it.
So it enables you to stop worrying or things like OK do. I need more cores? Do I need to move my SQL server to bigger. VM and just say OK. I'm focusing on my business. I'm looking at my queries. I'm optimizing my queries optimizing my index is not thinking OK do I have the?
To move to from 4 cores to 8 cores, so we have built in this international instance, so if you need more cores. You have just one slide that say, I want to go from 84216 core everything online.
So if you hear if you see some problems that some problems that you have in your everyday business probably managed instance and pass is solution for you.
Now, when we are talking about, but organization of SQL server. You always have 3 options. One option is to go to stay on premises and use SQL Server 2017, 2019 or whatever new version is coming and that that is fine choice but in this case you need to.
All these tasks that are shown on the in the first column like from application data maintains to Hardware Management Virtualization OS Provisioning patching.
Other options are to go to other cloud and use infrastructure. The service or platform as a service.
So we're not saying that pass is always better than IS or on premises your choice what you want to do and what you don't want to do so. If you have very capable network admins. Harder administrators who can really tweak your higher infrastructure, you can probably have better performance.
This is done in Azure or if you have highly skilled dbas who know how to tweak your database probably your on premise orias database might be better than pass.
But in cases that you don't have teams that are experts for virtualization. OS Maintainance, patching or you just don't want to waste time on this then platform as a service solution for you in platform as a service solution. We are implementing all this high availability attaching.
Bing virtualization and we're letting you to think about your data your application. So this is generally choice that you need to make what you want to do in the future.
Now, one thing that people forget and it's very important is that you can save a lot of value it pass in it managed.
We have something that's called age be and we have something that's called reserved instances.
So it would be really good to take a look at this becaus if you already have SQL server licenses on premises and you want to have reserve capacity for next to 12 or 3 years. You can have up to 80% of saving.
So people usually say OK passes something in a very expensive. We want less cores. But then they don't see that they have opportunity to lower the cost of path from 1000 from one K 2200 dollars just because somebody didn't see that this is opportunity that Azure gives you.
So if you're OK with this please. Go to Azure documentation, and see what is HB and what is reserved instance you can decrease your cost significantly?
And soon we will have special discount for dev test subscriptions. So currently we are enabling toured 5 types of description on Azure. And so we will have full dev test subscriptions enabled in all dev test subscription, which means that the price will be.
So, in dev test solutions you're not paying for license for SQL server. You're paying just for underlying infrastructure that we're running managed instance.
So these are some options that you need to be aware when you going to match instance because you can save a lot of money.
Another interesting thing that you should be aware is how you map your SQL server on premises licenses to Azure managed instance, so first Arthur managed instances enterprise edition of SQL server. There is no such thing like standard edition in Azure cloud, so even in Azure SQL, database if you're running.
You're getting enterprise edition of SQL server. The reason for this is that enterprise edition makes our life easier because for us is easier to manage enterprise edition, then to manage standard edition.
So if you have already have some standard edition licenses or enterprise edition license.
You can just transfer this to managed instance or a SQL database, and you can exchange one. Standard addition core to one general purpose. One chord in general purpose or one. Entrance addition code to one code in business critical, but still general purposes again enterprise edition of SQL.
So you are getting from standard addition, you're getting enterprise edition license in cloud.
Another option is if you already have enterprise edition of addition license. You can get 4 cores in general purpose for one core in Enterprise Edition.
So this is some mapping that you need to be aware if you're planning to move your on premises SQL server licenses to Azure cloud.
OK, so let's see finally some introduction. What is our SQL database so our signal databases. SQL server fully management SQL server that we're running other cloud and you have 3 options. There you have single databases. Elastic pools and managed instance SQL databases are therefore.
Long time and their build for user for new applications that are born in cloud or for applications on premises applications that are not using some special instance level features or some features that are not supported single database like simulated is supporting full T SQL server.
Well, that you need for your application. It only don't support. Some instance level features like linked servers service brokers. That kind of thing that are very specific for SQL server instances.
But in most of the cases single database our way to go for all new applications because they have surface area that works in 95% of the case.
Elastic pool is 1 type one way to organize your single databases signal to resource governance risk pools in SQL server. We could just pack multiple single database in one pool, so they can share resources.
And finally managed instance is actually entire SQL server instance hosted in Azure cloud. That has nearly 99% of compatibility your SQL server engine and it is designed to enable easy migration from your on premises to Azure cloud.
Now, why do we need merged instance?
So the reality is that if you want to migrate to cloud you need to make some changes.
Becaus cloud is really different environment than your on premise environment.
Now this journey might not be easy. In some cases, be cause. Some features in in cloud are not supported like SQL agent. If you want to go to our SQL database. There is no SQL agent. So if you have some maintain its task. You need to use something like Azure functions, just to call some stored procedure that will.
Which is not bad because other functions could do everything that SQL agent can do if you just execute physical tasks and their cloud. Born have better availability that SQL agent. But in some cases, the amount of time that you need to spend to rewrite your SQL agent jobs to other functions is just too.
If you have some if you want to use restore you cannot use it in other single database. Becaus single database don't support all SQL server features and restore is using binary image of your database in trying to restore all features that you have on premise.
Well see if you have some features like CLR, they're not supported in SQL database. So if you have something like this and you really need him, then SQL database was not choice for you.
And this is the reason why we had to implement new type of Azure. SQL database called Management says that will enable easy migration from your own premises to Azure cloud. There we are supporting SQL Agent Native restore CLR and almost all features that you have in SQL server on premises.
So here is that managed instance enables you easy lift and shift. It has nearly 100% compatibility so in most of the cases. You don't need to do anything to migrate your SQL server to manage distance. Now, nearly 100% it still doesn't mean that there are no differences because.
Surface area in SQL Server is very big so even 1% of differences might be still huge difference. So we're not supporting things like features that are dependent on windows application like you don't have windows logins. You need to switch to ad logins because this ad is actually logins in our.
We are not supporting some windows specific features like access to local files. You cannot do bulk import from C Drive. You need to use bulk import from Azure Blob storage and this is 1% that you need to change or you need to consider how to re fact.
Move to Azure cloud, but still most of the features will just work in managed instance.
Again, it is fully manners, so it's this combination of SQL Server in Classic Azure SQL database. So we have implemented high availability. Automatic backups and all other past features that exist in Azure SQL. Data is there already in managed instance.
We have insulation like managed instances hosted in Azure cloud, but is placed in your Vineet you have questions.
Yeah, so the question is what happens if you have SS jobs. I will talk about this later but yes. Sic supported because Azure data. Factory is supporting can host SSIS drops S packages and you can call you can call them from managed instance.
So this late.
So many instances placed in your V net. So it is not public resource. It has dedicated private IP that is defined by your your own subnet.
And he has very competitive and transparent business model that you will see later.
So let's see what is actually managed instance.
Unlike Contra SQL database that is a public services, which means that in our SQL database. We have set of public VMS where we are hosting SQL server database engine in managed instance. You're getting a set of your own VMS where we are installing managed instance for you so this is what we call tenant.
Whenever you create one or more better since you're getting Arthur VMS that is dedicated for you and nobody else can place any other resources on this VM S so you have full tenant isolation from all other other customers.
Let's more important this these VMS are injected in your V net.
So you need to create your Azure vnet, you need to create your subnet. You need to prepare network rain range where managements will be placed and we're just injecting VMS with managed instance inside of your Vin it this way, you're getting a full logical network insulation Becaus Jorg.
IP addresses that are assigned to managed instance.
One thing that we need to have is access to public Azure Services. Manage your control your managed instance, so we need to have access to services like service valves blob storage. Some management service that are controlling your instance because we need to do.
To Azure Blob storage, we need to send Telemetry to our services in order to find out is there, something wrong with your managed instance. Do we need to do failover? Do we need to? Do some maintain stuff or we need a channel. That will send updates an automatically update Patch your OS your database engine so they need to be channel from you.
Related instance to Azure to Azure services.
There is a concept to energies network security group groups in Vineet, where you can control who can access your managed instance, so you have full control over this. You can say. I want to prevent management access to manage this to some IP addresses or?
Changes, which is great for you, but there is some exception. You cannot do something that will block our access to management service, so since you are owning Vineet. You can easily say OK. I want to prevent all ports that managed instances using to send Telemetry to Azure Services man.
Because we're not getting heartbeat connection from errors distance. We think that it doesn't work.
We cannot solve this because by design, you own the network. You are owner of your network traffic so in some cases. You cannot do something that can block access from management or other services.
When we can see.
Yes, we are so when you create a vineet their recommendations. I will show this in the next example.
And also there are some things that you cannot change so we have some rules that we have built in into Azure Vnet and we are preventing you to do something that can block access from entrances to other services. But for some cases, we cannot block so I will show you later.
And also you need to be aware of this that. You can block yourself. So if you have managed instance and you want to access your own premises. SQL server with link server. You need to open ports for SQL server. If you want to use DB mail. If you want to use transactional replication. You need to open ports for like inbound and outbound port for this.
Only in this.
Good question power BI so integration with power be. I will be better in next couple of months, so power be. I need to access public IP address currently so currently if you want to use power. BI if it managed instance. You need to install on premise gateway that will route everything to your own premises and then go back.
But in the next couple of months. We will enable public endpoint so you can configure public endpoint in power be. I can directly go to your managed instance, I guess it will be available next couple of months.
So if you have other resources in your V net or in other vineet like you have web apps. You have VMS with application. You can just connect your 2 of Nets within a 2 minute peering and you can access your managed instances any other resource in your virtual network.
Or if you put your resources in a different subnet in your Vineet your VMS and web apps can directly contact your managed instance like any other resource. One important thing here if you have a subnet for managed instance, you cannot place anything else in.
So we are assuming that if we have a subnet you have placed managed instance, we own. The space so whenever we need to fail over instance to some other others. We are assuming that all IP addresses in this subnet are available for us, so you cannot place VM into subnet where you have placed your management.
So all other resources need to be pushed away to other subnets.
And also, if you have your on premise resource like if you want to access laptop. You can set up VPN Express Route Gateway Point to site collection site to site connection. So many instances, not different than SQL server in Azure VM. So it's just one resource hosted in cloud.
Connect you can reach it from your network.
Also, if you have a resources another like if we have Azure Web apps. You can do something that they call Vineet Integration, where you can have public also web service that is integrated with your Vineet and you can directly send queries from your web app to your managed.
What if you have resources in another vineet like VMS app services you can just establish peering or VPN channels between 2 minutes and these applications will see or mentions is as yet another resource.
And also you always have options to connect your on premises to manage this using express route or point aside gates.
Now I only told you that match instances. Easel Eighted in dedicated to you and there is something that we call virtual cluster virtual cluster is some structure that is placed in subnet where we are hosting your managed instance, so this is structure of virtual cluster.
So virtual cluster is placing, Vineet and in that virtual cluster. We have a set of virtual machines where we're installing SQL server, and that is running your database.
Now here you can see in this bigger bigger part that this is Azure. VM there, we have standard SQL server database engine and something that we call management agent or or node agent. This is a process that communicates with SQL server, and send some Telemetry to Azure or control.
Would restart or when backups should be done. So it is like controlling agent for your managed inst.
We have public IP address currently that only we can use be cause. We need to access your cluster through public IP. But we have very strict certificates and only Microsoft Kinect is this public IP address and it is used only for managed.
Then we cannot do anything else through this public endpoint.
If you want to access your managed instance, you have this classic TDs endpoint that is placed on your private IP because it is placed in your private subnet and this tedious send point is going to something we call internal load balancer in gay trees that are accepting this SQL query request and then just routing.
Some of the instances or some of the VMS inside of this virtual cluster. So here is that if you want to access this my MI cluster ID database windowsdot.net. The request is going to this internal load balancer that will find what VM is hosting the measures that you want to uh.
Then the traffic goes to gateway and Gator is going to manage the instance to to execute very end run it.
Now in the Cup artistical database has a single database has ability to bypass this gateway, which is used. If you it's useful if you want to not to have these 2 hops from your load balancer to SQL server. Database engine and we will enable this in next month, so this is a configuration that is recommended for.
Applications or where applications that need a lot of low latency that have low latency network requirements. But in most of the cases in in our SQL database gateway solution is the best option for most of generic workloads.
No cluster so the question is, is cluster ID regenerated know it is generated when you create first managed instance, then we're creating first cluster and then we're injecting them. An instance in that cluster so every managed instance that go into the same subnet will get will be placed in the same cluster.
Oh, so question is when I we drop less managed instant recreate so currently we are keeping cluster 412 hours and then automatically drop it.
But soon you will have ability to drop your own visual cluster.
The fact is that creating virtual cluster is very expensive operation because we need to put build we need to configure everything so this is the reason why creation of first match instances slower than others. So we are retaining this virtual cluster for some time just to just in that case if you're dropping last instance and you.
Couple of hours, you don't need to wait again everything to initialize but for some period it will be retained.
Yeah, yeah.
Now.
The biggest problem that people have managed instances how to configure it because usually people who want to use managing start DBA or?
Yeah. Oh. Sorry.
Huh.
Yeah.
So so the question is could we set up low latency for just some instances, yes, this low latency will be enabled for instance.
So it is configured for instance, always but you always have availability group, so build groups of his own is always there, no matter do you have direct taxes or gateways?
OK.
OK, so when you create managed instance the biggest challenge is how to configure virtual network and how to set up everything so my recommendation would be just go to our SQL documentation because there we have documented all best practices and shortcuts that you can use to easily create Nash dances.
You don't need to read network documentation to see what you need to configure format and since you can. Just go to documentation and you have here this create new vinette and subnet for managed instance. You just need to press this deploy to Azure button. It will involve some Azure Resource Management template that will create Vineet.
In another subnet for application and it will configure everything that is needed for your managed instance, so if you don't. If you're not networking expert. Please click on this blue button and just deploy your network environment.
If you have existing subnets and existing minutes also documentation. We have power shell scripts, where you can just say this is my subscription. ID resource group name vitro network name and submit name in this script will go to your subnet see is it able to accept mention instance.
It will recommend you what needs to be changed.
Or you can use this script automatically to change and configure everything in your subnet so we're checking things like Are they UDR do you need to remove sub service endpoints so this very specific things that it's very hard to debug in trouble shoot in some cases, it is easier just to take the script.
And see what they are the problems in your subnet then just automatically fix.
Now, if you want to access your virtual your managed instance, you can use VM in Azure Vnet in Azure or you can use point aside connection. So when you create your first when you create your managed instance. You can go to this quick start guides and their power shell scripts for crew.
Virtual machines endpoint aside connection so if you're just use this script. It will be populated on your portal. We are populating subscription. ID resource group names everything that you need to do just use. This script exit with power shell, it will create VM with installed management studio that you can use directly to access.
Managed instance.
If you want to access your manage lists from your laptop you can establish this point to site connection.
Again, if you don't want to hassle with the network configuration, you can just go to portal take this script and execute it, it will create virtual network gateway to create certificates. You just need to download VPN client install it and just access your messages from your laptop so.
Creating network environment an axiom energies. This is very easy if you just follow documentation in portal by our experience. This was one of the biggest problem for customers who are starting with mercy instance because people want to use data base and they're not really experience with Azure Vnet and how to configure point to site network.
Usually they don't contact something somebody from networking team to configure this for them.
So let's see something.
Let's go shortly tool.
Instance configuration.
Now the easiest way to create managed instances just to go to Azure Portal say. I want to you. I want to create new Azure sequel, managed instance, you create put measure instance name admin and password collision so this is an important check collation and yours.
And use the same collation here because if you Miss Collation, you would have problem with you might have problem with queries that are using 10 DB or cross database or some system objects and this collection can be configured only when you create the instance, so once you create the instance. You cannot change collation so you will probably know that.
Changing collation SQL server is not so easy task, so it is not possible in management.
Yes, this is default SQL server college or Azure sequel, this default. Collation Yes, but it is not change. So it is. It was default. Yes, so we never changes because.
This is this is default. We are not we didn't change default collation ever. Although we have.
I think so.
Really?
Yeah, yeah, OK so I'm not sure about this is default. One so you just check your collation.
So you can you just need to convert it when you create new management and so that's
Yeah.
OK, so you configure location and here is one additional shortcut. If you don't have prepared virtual network. You can just click here create new virtual network. It will create some default virtual network and prepared submit their management this will be placed.
So everything else is.
Just straight forward this is the same thing that you have on Azure. SQL database you can choose between general purpose in business critical.
Truth how many calls you want, but storage you want here and if you have sequencer license. You can click this save money button that will decrease price for not half but 30%.
Now this is not critical so if you missed number of course, you can always change. It later becaus migration from one ask you to announce to his fully online. So there is no down time. Your instance will not be online instance will not be offline, we are.
All I migration from one VM to another VM that I will show you later. How you do it.
OK, I will talk now about 3 steers and difference between general purpose business critical and hyper scale. So currently managed instance. We have 2 service tiers. General purpose in business critical in Hyperscale will hopefully come in next couple of months.
General purpose is thier that is designed for most of the workloads so if you have SQL server on Azure. VM and you have general purpose in most of the cases performance should be the same because they're using the same architecture that your hours later business critical is dizzy.
The workloads and for scenarios when you need fast recovery and In addition, you have one free read only replica so the idea. Here is that a business critical has built-in availability group and local SSD storage that enables you to run very fast workloads and.
Always on availability we have one spirit replica that we can get you can get for free.
And hyper scale this is a new student will come soon. It will it is designed for very large databases very large instances up to 100 Terabytes designed for all TP workloads and in this you, you can add as many as you want read only replicas.
So I'll just quickly go to description of this service tiers so in general purpose.
We have separation of compute and storage. We have EMS that are stateless that are running. SQL server database engine. All caches are there there and we have all MDF and LDF files stored on Azure Premium storage so in this case you something so.
Compute and storage so if something happens, with SQL server engine. We're always keeping some redundant. Nodes with pre installed. SQL server database engine. So if we have some of this compute nodes, failing down.
We're just pushing new node with SQL server engine code and just attaching all MDF and LDF files so in this case availabilities. By this using this separation of computing storage. So whatever we write in Azure Premium Storage. It we're sure that it will be.
And you something crash in SQL server database engine. We always have spare sequel server know that we can put instead of the old one.
So if you take a look at Premium Storage.
So we have this separation of status compute an Azure premium, storage and on Azure Premium Storage. We're putting all this MDF and LDF files so whenever we write something in data file using checkpoint or write something log, Azure Premium storage is internally replicated so Azure Premium Storage.
So their guarantee that whatever we right into the file will be replicated in safe. So we can be sure that whatever is stored will be preserved.
Now, one problem here is that in Azure Premium storage throughput in iOS depends on the file size.
So, in Azure Premium Storage. If you have bigger files you get more throughput and more IOPS. So if you have smaller data files. You have some bottleneck in my office or throughput and in this case, one solution for this is just to extend to increase the file size.
The file and get more throughput in IOPS.
And one important thing is that all databases are replaced on remote storage. Except, of Tempdb. MDB is placed on local SSD because we need low latency access to 10 DB in this case, and we don't need to have ability on TV so it MDB is always exception.
So general guidelines for general purposes that you need to be aware that this is cloud environment. So if you're running application. You need to be aware that something something can break always so if you have you can have always connection break network problems? There can be some failovers?
Aware of this.
In that case, our recommendation is always tried to use shorts and section in Batch. Updates never use something like long running transaction like big intersection start load for 12 hours and then close.
So I also use partitioning if you need to rebuild indexes, which is by design. Long running operation try to use partitioning. Just rebuild each individual partition also try to use compression and column store because the best thing, that you can get bigger problem in.
Q is latency between compute and storage so you can decrease this latency by using compression of column store that will be good for your application.
Now, what is the problem with long running transactions if you start if you big intersection and start some long boat load?
In the after a couple hours if you happen that we need to fail over your instance or something happen.
In this case SQL server database engine is using this process to when it need to attach your MDF and LDF files to new instance. First, it needs to analyze your log files to see are there some uncommitted intersections then? It goes to the last uncommitted transaction and?
Performing redo of all transactions and then it goes to the last end of log. You need to undo all transactions that are not closed that are not committed this is the problem becaus, especially in this redo face becaus database will not be available.
Right because SQL Services is trying to reapply all uncommitted transactions from your log file.
This is one of the biggest problem in general purpose and this is the reason why we're adding accelerated database recovery and selling the database recovery is new things that is available in single database and it will will need shorter time to analyze logs and redo in undo transactions it is not.
Full solution of the problem, so we're still recommending you not to use long running transaction because it can affect your availability after failover. But in most of the cases if you really need to do something like online transaction this accelerated database recovery will help you to more quickly recap.
If you cannot avoid this recommendation is to go to business, critical business critical instead of separation of computing storage. We have always on availability group, so we have one primary replica for read write role in 3 secondary replica that are getting old.
Is there an one of these secondary replicas available for read only queries?
So this is the reason why you are getting free of charge one secondary replica in this skew.
So advantage of this model is that if we need to fail over primary replica or something happens here. We don't do this? Do undo phase. Becaus all rogue records are already on secondary replicas. So, technically, we just need to switch primary to secondary.
Adjust IP address so on internal load balancer road in gateways, so this is Q. That is built for fast recovery. You will get like minute or second of recovery in a general purpose this will be subsecond.
Yeah.
That's good crashing other synchronous mode, so transaction processing business, critical so if you write something into primary node we are.
Sending the same log file to all secondary replica and this is synchronous, but we're just writing. This data in log file and not applying to database engine because we need to as fast as we can to get response from this replica so when we have at Lee.
3 or replicas answer that they are written the log into log file. We will commit a session so that part of writing in secondary log file is signals, but then secondary replica is in the back of the reading log file and just redoing all of so.
Things queries on secondary replica you will see some lag.
Because this is trade off between speed and availability. This 2 of 3 is pretty crazy. Just know that we have quorum and then we're letting second replica just to apply the changes.
Game.
So average latency is here or less than 523 millisecond. It really depends so you must be aware that yes, we have super fast SSD in business critical on primary node. But the time that that is required to commit and section is time need to write to local SSD and.
Remote test is this.
Or other SS DS to the right walks.
Now, short hyperscale hyperscale is new student is coming soon in couple of months and it is built for very large database.
So if you remember the general purpose architecture. We had separation of compute and storage where we had stateless compute and data placement storage. Now we have limitation in general purpose because we can have up to 8 terabytes of data? What is the reason for this one reason is back up?
Sure, that we can always have a full backups log backups. And if you have 100 terabyte database will just do backups will not have resources to anything else in another problem is that in this compute we have well in the best case like half of.
So, in the measure instance, you have memory that is proportional to the number of cores so you're getting 5 gigabytes per core.
Meaning that if you have 80 core instance, you're getting like 400 gigabytes of Memory. So imagine that you have 8 terabyte instance and in half of terabyte memory in classic all TP workloads. You'll have problem with page like life expectancy becaus that care.
Computer will not cover all data that you have remote storage.
So this is the reason why we're adding.
These hyper scale here we have a separate page. Servers page servers are separate SQL server engines that are running below. This compute and they're running SQL server database engine processes and each of these database engine is can one terabyte of data.
So this means that if you have 100 terabyte data 100 terabyte instance, you will have something cast in your compute and if something is not in your compute it will be just read from this second level page servers, so this way we can handle larger database that go.
Terabytes.
And also one important thing is snapshot backups. We're this architecture enables us to avoid streaming backups. Like backup to URL and we can just take a snapshot backup on other storage so in this case. If you want to do some recovery or point in time restore it will happen in less than minute, 4.
10 of 50 terabyte database.
Now, another important thing here is how we are handling read only replicas, so you can also have read only replica that are just reading data from this page servers. So you can add as much as you want. But we don't elect because that will just take this read only data.
And also one of the big change here is how we handle logs. Unlike general purpose where we are storing log data into log. Files on our Supreme storage here, we have dedicated lock service that is just collecting log records and it's true that you can get with this log service should be much better than.
Why was directly into low storage so in this case? Whenever you commit some transaction it will just go to this log service and lock service video updates. This underlying SQL servers and read only replicas, so in this case. This is a change of nature that enables us to get.
Bigger databases, but just be aware that this is not a solution for data warehousing because people when people see that this is 100 terabyte database. They usually think, OK, I will run. My data warehouse here. Problem is that this is still OLTP workload because if you have some operation like.
Entire database you will get you will not get anything your cash and compute you'll need to put down predicates on all these underlying search engines and you will not get some benefit from this, if you have classic data warehouse workload. You need to go to other data warehouse because other data warehouses that massive parallel processing.
So this is mostly for all classical TP workflows or Hibrid HD photos that are working with very large database.
So I'll just.
Go shortly to migration process because we are close to the end.
So if you want to make it to match the instance, you have 2 phases assessment in migration. Instead of reading documentation and seeing what are the difference between managed instance then your SQL server? It will be better to use data migration assistant so data migration assistance. You just want tool that you can download to your SQL server data.
Target is managed instance and it will automatically say what are the differences that you need to resolve and can you make it to mention instance?
You can use data implementation assistant or some benchmark tools like 100 DB or yesterday. I found this workload tools for one MVP spaghetti. DBA that are really interesting if you want to run your workload and just replayed on managed instance.
If you want to do migration you have backup restore or data migration service.
So generally you're using backup restore if you want to try manage the instance becaus. It's faster weight fastest way to migrate to managed instance.
But it is offline, so time when you're back opinion, restoring your database. You should not use your application and data migration service will do fully online migration. It will use something like log shipping. It will just take first backup and just take your logs take your.
Also and log backups in just upload them to manage this.
So I think the time is absolute if you have any questions, I will be happy to answer that now.
So the question if we migrating to a business critical from on premises.
Across.
Yeah.
So if you want to run something in parallel one option is to use transactional replication. And then but I think it's better way would be to use this database is plantation system that will record your workload and just run it because there is no something like parallel workload.
Question.
Yeah.
Can you guarantee?
I think so. Yes.
I can I don't need to check my?
Yes, so I think that we can go to sleep because the same approach. We're using our SQL database. So I guess that there will be the same problem in our SQL database. But yes because database ideas. Some logical information that is stored outside of managed instance. We have this management service that has registered all database so I'm really sure.
He will not change, but I will need to double check.
Special.
So the question is standard latency for general purpose. So it is documented on our side, so we expect latency or like 5 milliseconds 10 milliseconds on general purpose and below 3 milliseconds or business critical. But everything is documented. It's better to check their because it might be changed.
So question is how to handle SSIS packages so Arthur Data Factory is enabling you to upload SA packages to Azure data. Factory and their guarantee that there are no changes. You can just run them there on managed instance you can install SSI SDB.
The and then you can just well run Classic sequel, essays packages from using ADF.
As far as I know there are no changes that.
Yes, if there is some yes.
I'm not sure about this.
Guarantee secure.
I think that there is no some some check in emergencies for this so if you have something.
If you have something that you're using on premises. Some tool that is checking this. It should work on measure instance. It's like. But we don't have anything built in for this.
Well be cause we need to create VM that is injected in your so question is why it takes so long to provision. Management is in our SQL database. We have prepared VMS that already and with running SQL server database engine so in SQL database. You're just getting one of the entries from the pool.
We're taking you VM and just injecting it to your Vineet. We're installing SQL server. You are put in the latest bits so it takes some time.
OK.
Can you repeat this?
Resolve 3 IP addresses.
So that's not talking about requirement, so if you have business critical. We need at least 4 IP addresses for each separate IP addresses for second general purpose. We need some extra IP addresses for this pair nodes in Hyperscale will need extra IP addresses for page servers because page service.
Database engine so you don't need 2 or 3, maybe this is it's hard to determine exact number. We're just saying OK. Please take at least 2 X IP addresses for general purpose in 4 X 4 business critical.
You mentioned Tempe pays on local SSD? What is the Max size?
So what is the Max size of MDB on general purpose is proportional to number of cores so you're you're getting fairly 4 gigabytes per core.
And on business critical is just compete with other databases. So if you have one terabyte business critical 10. DB can go up to one terabyte.
OK, there's no other questions. Thank you for coming to the session.