We have a lot of clients using our SQL Server Managed Services here at Red9.com. It is worth saying, that to this day, we haven’t found a single case where SQL Managed Instances make sense. Maybe it’s our client set. It’s true that our clients tend to be more complex environments that require all bells and whistles available. As of this writing, we don’t have a single client where we are using SQL Managed Instance. We do have some client that have Azure SQL though.
Pros and Cons
Here are few notes I took at SQLSaturday Atlanta about Azure SQL Managed Instances.
Today there are two managed db options in Azure:
- Azure SQL
- and Azure Managed SQL Instance
Azure SQL Managed Instance vs Single database
Azure SQL database
– simple, easy
– most things are managed like backups. This is a problem though as if you want to log ship, migrate out, or do something more advanced – this gets tricky.
– backups are fully managed
– sql agent don’t exists… ummh…ok…
– no cross db communication
– cant power down (so you cant stop billing)
– cant restore native backups
– to import into Azure SQL – you have to use Tasks -> Export -> script out all objects.
Use case that works well:
– when building new app
– limitations make migrating existing apps close to impossible (that means no big clients will go here for existing heavy dbs)
Azure SQL Managed Instance – PROS & CONS
– provides the best of both of the past offerings
– infrastructure managed by Azure (not sure this is good, because now I don’t know if Azure set Lock pages in memory, maintenance volume GPOs on, or power savings are set to Balanced mode. All I can do is to just trust them. And I am not there… yet.)
– no more Win or SQL patching – nice! But it doesnt seem like I can chose WHEN patching happens and I have heard SQL going down in mid business day because Azure autodecided its time to patch your instance up
– supports multiple dbs
– Azure SQL Managed Instance cross database query (cross db communication supported)
– SQL Agent available
– lift & shift migrations possible
– backups managed by Azure
– COPY_ONLY backups can be run by ad hoc
– 98% of features there (not convinced its really 98%, or closer to like 85%). Also the missing 2% need to be identified, as one missing item could quickly become deal breaker.
– June/July when Managed instance should become available
– if you have core licenses already, you can migrate them (kind of) to Azure
– if you have MS contact/manager, you can let them know and he can help expedite this
– Azure SQL Managed Instance High Availability and Disaster recovery (many options available)
– Some features not available – Azure SQL Managed Instance limitations
– limited to SQL Authentication. No Active Directory. This one is big one! Work arounds?
– currently in preview – only in General Purpose tier available. As of May 19, 2018, in limited public preview, so you cant get this yet
– cant shut this down (so billing keeps on ticking)
– in memory file groups must be empty in preview
– initial build currently takes ~24h – additional builds in the same subnet takes 3min. Not super bad, compared to what usually takes to get new server provisioned
– HA is built in and cannot be controlled
– password has to be min 16 characters long 🙂 – Microsoft should make this 25, because at this point number of people typing passwords in is decreasing, so why not make max a default
Azure SQL Managed Instances – Requirements:
– Azure vnet – I like this one. Makes me want to do this everywhere to just separate traffic from Netflix vs. stuff I care about.
– subnet and routing list
– additional subnet for Azure VM connecting to managed instance
How do you migrate to Azure SQL Managed Instances. Here are few options:
– restore from native backup written to Azure Blob Storage
– Azure Migrate available for VMWare environments
– MS plans to make Azure Migrate available for on-premises and Hyper-V environments
1. Noisy neighbors – we ran into weird performance problems in Amazon AWS. You buy an EC2 server and on daily basis your performance fluctuates. But nothing changed on our end. Why?
After I got AWS support cornered/escalated, they go – “well it can be the neighbors on the same physical server.” Umhhh… yeah, not cool. I get that I am on a shared server, but I also get that I bought my CPU cores, RAM, etc. – so, no, I don’t really care about what my neighbors needs may be.
It just same as if you rented an apartment, one day you come back and find couple people inside, because apartment complex decided to Airbnb your space while you went to the mall. NOT COOL.
I bought my space – and I don’t want anyone there. Doesn’t sound nice, but that’s exactly what I want on my Production SQL Server.
There will be multiple managed instances on same physical server. So having a high fence around my server to prevent my resources being sucked out by other knuckleheads is important. I would like to see more data on how Microsoft Azure will handle this noisy neighbors. They probably thought this through, but I need data.
2. What does storage/disk IO throughput look like? I need more information about Azure SQL Managed Instance performance.
3. Does it make sense to keep splitting db into multiple filegroups, files to get more throughput? Does it make sense to have multiple db files in blob storage and how does that affect performance?
4. Emailing out. How do we handle emailing out from server? I like to get some reports/alerts, so yeah, I am going to need to email out.
5. Do I have any access into OS? I think the answer is No, but still would like to ask. Can I at least see OS in read-only?
6. What other Azure resources are needed to launch this for small setup?
7. If I need to schedule PowerShell script to run, can I do that? And no, not SQL PS, but real full featured PowerShell…