healthcheck-dotnet-mssql

To add a SQL Server readiness check to ASP.NET Core, register a connectivity probe using the AspNetCore.HealthChecks.SqlServer library within your health check pipeline. This exposes a /health/ready endpoint that returns healthy status only when the configured SQL Server database is accessible.

The best way to verify SQL Server connectivity in a .NET health check is using a lightweight SELECT 1 query. This approach checks database accessibility without adding performance overhead to your application's health check pipeline.

Yes, this SQL Server health check works with the Jarvis framework. It registers the readiness check using the official AspNetCore.HealthChecks.SqlServer library, making it compatible with the Jarvis framework's health check pipeline for ASP.NET Core projects.

You configure a /health/ready endpoint for SQL Server by registering a readiness check that uses your pre-configured main database connection string. This ensures load balancers and orchestration platforms only route traffic to instances with active database connections.

An ASP.NET Core application needs a database readiness probe to ensure traffic is only routed to instances that can successfully access the primary database. This prevents routing requests to instances without active SQL Server connections.

Yes, you can use this health check skill with .NET 9 backend projects. It is designed for ASP.NET Core projects built with the Jarvis framework, adding SQL Server readiness validation to the health check pipeline for load balancer traffic routing.