diff --git a/Directory.Packages.props b/Directory.Packages.props
index c9ad0acf..4740412e 100644
--- a/Directory.Packages.props
+++ b/Directory.Packages.props
@@ -89,6 +89,12 @@
          document (the XML formatter ships in a third, unreferenced package) nor frame the /sample
          multipart stream socket-free. The driver uses HttpClient + System.Xml.Linq only. See the
          Task 0 CORRECTION block in docs/plans/2026-07-24-mtconnect-driver.md. -->
+    <!-- Fully managed PostgreSQL ADO.NET provider for the Sql poll driver's PostgresDialect
+         (NpgsqlFactory.Instance). No native libpq / client install — the same "managed only"
+         constraint that rules out Odbc. Referenced by Driver.Sql.Dialect alongside
+         Microsoft.Data.SqlClient; consumers inherit it transitively. Latest stable, shipping a
+         native lib/net10.0 TFM. -->
+    <PackageVersion Include="Npgsql" Version="10.0.3" />
     <PackageVersion Include="Novell.Directory.Ldap.NETStandard" Version="3.6.0" />
     <PackageVersion Include="OPCFoundation.NetStandard.Opc.Ua.Client" Version="1.5.378.106" />
     <!-- Core carries Opc.Ua.StatusCodes, the oracle StatusCodeParityTests checks the drivers'
@@ -97,6 +103,11 @@
     <PackageVersion Include="OPCFoundation.NetStandard.Opc.Ua.Core" Version="1.5.378.106" />
     <PackageVersion Include="OPCFoundation.NetStandard.Opc.Ua.Configuration" Version="1.5.378.106" />
     <PackageVersion Include="OPCFoundation.NetStandard.Opc.Ua.Server" Version="1.5.378.106" />
+    <!-- Fully managed ODP.NET Core for the Sql poll driver's OracleDialect
+         (OracleClientFactory.Instance). The ".Core" package is the 100%-managed driver — no Oracle
+         Instant Client / OCI native install, matching the Npgsql constraint above. Latest stable of
+         the 23.x (Oracle 23ai) line, which ships lib/net8.0 + netstandard2.1. -->
+    <PackageVersion Include="Oracle.ManagedDataAccess.Core" Version="23.26.300" />
     <!-- OpenTelemetry.Api < 1.15.3 has GHSA-g94r-2vxg-569j (header-parsing memory DoS). The trio
          is pulled transitively at 1.9.0; pin to 1.15.3 (matches the Extensions.Hosting pin below),
          applied via a direct PackageReference in the Cluster project so the server stack inherits it. -->
diff --git a/src/Drivers/ZB.MOM.WW.OtOpcUa.Driver.Sql.Dialect/ZB.MOM.WW.OtOpcUa.Driver.Sql.Dialect.csproj b/src/Drivers/ZB.MOM.WW.OtOpcUa.Driver.Sql.Dialect/ZB.MOM.WW.OtOpcUa.Driver.Sql.Dialect.csproj
index dd9f264b..bf77262f 100644
--- a/src/Drivers/ZB.MOM.WW.OtOpcUa.Driver.Sql.Dialect/ZB.MOM.WW.OtOpcUa.Driver.Sql.Dialect.csproj
+++ b/src/Drivers/ZB.MOM.WW.OtOpcUa.Driver.Sql.Dialect/ZB.MOM.WW.OtOpcUa.Driver.Sql.Dialect.csproj
@@ -21,8 +21,13 @@
     <!-- The reason this project exists rather than the dialect living in .Contracts: ISqlDialect
          exposes DbProviderFactory and SqlServerDialect returns SqlClientFactory.Instance, so the
          provider package is unavoidable here. .Contracts is deliberately provider-free. This is
-         the same shape as Driver.Mqtt.Transport, whose BuildClientOptions returns an MQTTnet type. -->
+         the same shape as Driver.Mqtt.Transport, whose BuildClientOptions returns an MQTTnet type.
+         PostgresDialect and OracleDialect land here for the same reason, each returning its
+         provider's DbProviderFactory (NpgsqlFactory / OracleClientFactory); both packages are fully
+         managed ADO.NET drivers, so adding them costs no native client install anywhere. -->
     <PackageReference Include="Microsoft.Data.SqlClient" />
+    <PackageReference Include="Npgsql" />
+    <PackageReference Include="Oracle.ManagedDataAccess.Core" />
   </ItemGroup>
   <ItemGroup>
     <InternalsVisibleTo Include="ZB.MOM.WW.OtOpcUa.Driver.Sql.Tests"/>