In a previous article I described how to configure an Azure SQL database failover group for high availability across multiple regions. But what if you want to limit network traffic to a database in this failover group to only your private networks? In this article I show how to make a SQL database failover group reachable via the Private Link service and make sure the database stays reachable after a failover.

Last week I received an invitation for a social work meeting about "Pixel art in spreadsheets". I thought: "How hard can it be". Well, it is about 25 lines of C# 9.0 hard! 😁

With an Azure SQL Database, Microsoft is already providing high availability with an SLA of at least 99.99%. But if you want to prevent to be affected by a large regional event or want to meet regulatory demands to be able to execute failovers to another region, enabling a failover group is the solution for you. In this article I will show you how to create a SQL database failover group in two regions using the Azure CLI.

To capture images in my applications, I use the VideoCapture class of the EmguCV library, an OpenCV wrapper for .NET. To choose a specific camera, you need to supply an index value. But getting this number is not straightforward, and as this number can change over time, it might break your application in the future. So, what if we could use the actual name of the camera instead of the index value? In this article I will show how to achieve this.