Reference
Supported databases and aliases
List the native ADO.Net providers and how to load them
On this page
An ADO.Net data provider connects to a data source such as SQL Server, MySQL, PostgreSQL but also ODBC and OLE DB data source, and provides a way to execute queries against that data source in a consistent manner that is independent of the data source and data source-specific functionality.
DubUrl still requires the ADO.NET provider package and registration of its provider factory.
Learn how to install and register a provider.
To embrace the world of DubUrl, you need to follow some conventions regarding the way you’re providing your connection URL. The table bellow is listing the different aliases than can be provided in the scheme but also the name of the ADO.Net data provider package and the name that you should use as the provider invariant name.
List of Native ADO.Net data providers
Additional packages
For encrypted DuckDB files, add DubUrl.Provider.DuckDb.Native alongside the DuckDB family provider and driver, or install the native DuckDB connector archive. Encryption requires native DuckDB 1.4.0 or later. The prepared connection remains a DuckDBConnection subclass.
For SQLite, install the full Microsoft.Data.Sqlite package to include the default native SQLite bundle. If you deliberately use Microsoft.Data.Sqlite.Core, configure its SQLitePCLRaw provider separately. Do not copy DLLs manually as a general installation procedure.
Example
See Your first database connection for a complete PostgreSQL example, including package installation, explicit factory registration, and disposal. Other native providers follow the same sequence using the package, invariant name, and scheme listed above.