Now that we have a Managed Instance built, the next question is how do we get data across? I will break this up into separate posts but the lesson for this blog post is ANALYSIS FIRST!
Honestly, there will probably be less work needed to make the data compatible for Managed Instance, this is very true if comparing to the true PaaS offering of Azure SQL DB, but we should always check before migrating.
First step login into the Azure portal and find SQL Managed Instance and click create. Yes you can find these tutorials all online but this is my thinking and opinions on some key areas.
After many years working with different “flavours” of SQL server in Azure from its true PaaS form to SQL server in AKS (Azure Kubernetes Service) it’s time to look at SQL Managed Instances – you will notice that I call it SQL MI.
Just some handy commands to use via kubectl. I found these useful for various reasons so hopefully you will too.
Last week I created the below with a dummy database and is something that I will do against SQL server but this time that has a persistent volume claim.
So, the point in the previous blog post was to leverage Persistent Volume Claims – PVC for data when using SQL server that it is needed in a stateful manner. But what happens when we don’t create SQL server in AKS without a PVC?
Following on from my last post after creating AKS, I now want to work with SQL server. First step, load up Azure cloud shell.
What is Azure Kubernetes Service? Probably makes sense to tell you what Kubernetes is first. As Kubernetes states themselves “also known as K8s, is an open-source system for automating deployment, scaling, and management of containerized applications.” If you want to dig into the depths then head over to Andrew – http://www.dbafromthecold.com
In the last post we built an image of SQL server 2019 Linux hosted in Azure Container Instance for fast access to SQL server. So, your next question is probably, lets see some database action?
Being heavily involved with Microsoft Azure and database technologies it was only a matter of time that I would enter the world of Azure Container Instances (ACI). The same could be said about AKS – Azure Kubernetes Services, but that for I have used this technology to deploy ML models to. Anyways, going back to ACI – why would you be interested?
All About Data 