Skip to main content
N
About

Decision guide

Database client packages for .NET

Even when ORMs are used, direct ADO.NET clients remain a critical layer for connection behavior, resiliency, and diagnostics. Choose provider packages that match your engine roadmap and operational requirements.

5 criteria3 packages5-point checklist

The decision to make

Which database client package should your .NET service standardize on per engine?

  • Primary relational engines in production and migration plans for future engines.
  • Connection pooling, retry behavior and transport security defaults.
  • Support for async I/O, bulk operations and command timeout tuning.
  • Instrumentation and logging hooks for troubleshooting production issues.
  • Compatibility with your ORM, micro-ORM and migration tooling.

Shortlist and trade-offs

These options are starting points, not an exhaustive market list. Verify the current release, compatibility, license and advisory information for your project on the linked package pages.

1

Microsoft.Data.SqlClient

Modern SQL Server data provider for .NET with active support for SQL Server and Azure SQL scenarios.

Inspect package
Best fit
Workloads running on SQL Server family platforms that need current security and connectivity features.
Validate first
Provider behavior and defaults should be validated during major version upgrades.
2

Npgsql

High-quality PostgreSQL data provider for .NET with strong performance and PostgreSQL feature coverage.

Inspect package
Best fit
Applications standardized on PostgreSQL that need robust async support and observability integration.
Validate first
Provider-specific data type behaviors should be tested when porting from other engines.
3

MySqlConnector

Fully managed async-first MySQL connector widely used for MySQL and MariaDB workloads.

Inspect package
Best fit
Services requiring reliable async behavior and modern .NET compatibility with MySQL-family databases.
Validate first
Engine-version and server-configuration differences still require integration testing in realistic environments.

Practical implementation plan

  1. 1Select one supported provider per engine and keep its version compatible with the runtime and ORM. Centralize connection setup, pool configuration, retries, and command timeout defaults.
  2. 2Apply least-privilege database identities by workload. Separate application runtime permissions from migration and operational-admin permissions.
  3. 3Instrument connection opens, command durations, timeout rates, and pool exhaustion. Investigate patterns with database-native monitoring and query plans, not application logs alone.

Common pitfalls

  • Giving the runtime application identity schema-owner or administrator rights because migrations are convenient during development.
  • Relying on provider defaults for TLS, pool size, retries, and timeout behavior without validating them against production load.
  • Creating a new connection string or client configuration per request, fragmenting pools and making incidents difficult to diagnose.

Before production

  • Connections use encrypted transport and credentials are sourced from managed configuration.
  • Runtime and migration principals have separate least-privilege permissions.
  • Pool sizing, timeouts, and retries are load-tested against deployment concurrency.
  • Provider metrics and slow-query diagnostics are available to operations.
  • Failover, rotation, and database maintenance behavior are tested or rehearsed.

When to revisit this choice

Revisit database client choices when changing cloud database offerings, introducing stronger compliance controls, or seeing recurring production connection incidents.

Data, method and limits

Sources: the public NuGet v3 registry and NuBrowse editorial review. Refresh: package pages read current registry metadata when viewed; guide text is revised separately. Method: the shortlist favours distinct use cases and spells out trade-offs instead of calculating a quality score. Limit: validate the specific version, license, framework and operational requirements in your project.