Many thanks to all who joined us for our webinar this week, “Edwin Sarmiento Presents: High Availability Options for SQL Server on Linux.”
We’ve had the privilege of having SQL Server MCM and Data Platform MVP, Edwin Sarmiento, join us for several webinars over the past years, but this was the first time we got to hear his personal thoughts and insights on SQL Server HA on Linux.
Apart from some misbehavior from Edwin’s Pacemaker cluster during his demo (we promise this was not planned), the presentation went great and we think it can definitely be of great value to anyone working on implementing HA in their SQL Server on Linux environment.
If you want a quick taste of what was covered during the webinar, you can view the full slide deck and a transcript of the brief Q&A session we had time for at the bottom of this page.
However, we highly encourage you to view the full recording, because Edwin is a very engaging speaker who doesn’t waste any time with filler. There is a lot of valuable information packed in our hour-long session—as well as some Pacemaker and DxEnterprise HA demonstrations.
You can access the recording here: https://register.gotowebinar.com/register/1178184287442912258
Please reach out with any questions you have at firstname.lastname@example.org.
Where can we go for support for Pacemaker if the cluster service itself is having an issue?
For one, if you’re leveraging Red Hat Enterprise Linux, Red Hat would have the support for that. Keep in mind that Pacemaker isn’t part of the Red Hat package. Cluster Labs is who created Pacemaker, so support would end up with Cluster labs. However, you would need a support agreement with them to do that.
Most of the time the risk with open source platforms—especially if you’re using CentOS like I am—is you’re going to be relying on yourself. You’ll be working on Pacemaker and relying on user groups and forums. This isn’t going to be acceptable for most enterprise customer environments. So more than likely you’ll want to go the supported route of Rad Hat Enterprise Linux with an additional support contract with Cluster Labs.
Is the Windows UI the only way to manage the DxEnterprise cluster?
No, you can also manage your cluster entirely from the Windows or Linux CLI, and you can also use Windows Powershell. The UI is just there and available for your use if you want it. It’s supported on Windows, and we also offer a mobile app to manage your cluster, receive alerts, initiate failovers, and do other things from your phone.
I noticed the instance was a default instance. Does it seem like we can have a named instance on Linux or that we will be able to in the future?
Keep in mind, SQL Server 2019 is only the second version of SQL Server on Linux. It wasn’t until SQL Server 7 in the earlier days of SQL Server where you had the ability to create a named instance. At this point you can’t really have a named instance, it has to be a default instance on Linux.
The way you work around this is by deploying SQL Server on Docker containers where you can expose different port numbers through multiple containers running SQL Server. However, you can’t really have a named instance, and you can’t have more than one instance on a Linux box if you want it deployed outside of containers.