I asked a question on Twitter yesterday: what is the best high availability option for a SQL Server 2008 instance running in Azure on IAAS?
If running SQL Server 2008 in an Azure VM (no SQL upgrade possible, extended support in place), is the best option for high availability Database Mirroring? Or something else I am not thinking of? #sqlhelp— Kendra Little (@Kendra_Little) January 31, 2020
And check out the magic of the sqlhelp hash tag, I got loads of answers! So many that I’m actually selecting a few here for the purposes of keeping this post readable. First, John Morehouse , a smartie and a consultant who does a lot of great work in the cloud and on-prem helped me figure out what would be needed for clustering (which isn’t something you can do simply with this version in an Azure VM)…
I belive you could also cluster it but you’ll need SIOS for the storage. I think. DisclaImer: I’ve never tried it. Mirroring should work as well and might be simpler. #sqlhelp— John Morehouse #getVaccinated for #JohnsDad (@SqlrUs) January 31, 2020
What Oscar said. There are costs involved with ASR or SIOS. Make sure you factor that into your analysis. #sqlhelp— Amit Banerjee (@banerjeeamit) January 31, 2020
And also Dr SQL himself, Glenn Berry chimed in – he is also a consultant and specializes in topics like high availability and performance.
As others have said, Failover clustering using SIOS for the shared storage. Instance-level protection, that would be easier to maintain than DBM. #sqlhelp— Glenn Berry (@GlennAlanBerry) January 31, 2020
Other folks responded as well. It can be so useful to get multiple perspectives on a topic, and I’m continuously amazed at how helpful folks in the Microsoft Data Platform community are when they can help out with a question.
Thanks to everyone who helped me out!