Microsoft SQL Server package v1.0.0

A dedicated least-privilege Microsoft SQL Server login held in the client's own secret manager. The adapter reads the material as strict JSON with exactly user and password, presents it only during the TLS-protected login and never interpolates it into a statement. A result that echoes the password is refused. Windows, NTLM, Kerberos, Entra and certificate authentication are not covered.

Draft awaiting owner review. Select the SQL Server adapter with native_executors.sql.engine set to sqlserver; every SQL capability in that deployment must then use a sqlserver:// endpoint, and a registration for another engine is refused when the configuration loads. The adapter (aaes/internal/connectors/native_sqlserver.go, microsoft/go-mssqldb v1.11.2, reviewed in ADR-046) connects only to the registered host, port and database. The URL path is the database, never an instance name: the adapter does not query the SQL Server Browser, so a named instance must be registered by its fixed port. It resolves the host through the connectors' pinned egress dial, and its dialer refuses any other host or port, so a routing redirect from an availability group listener or a failover partner cannot move the connection. It requires encryption with TLS 1.2 or later and the certificate verified against the registered host name, and refuses a server that declines encryption before LOGIN7, which carries the password. It uses SQL authentication only; a login name containing a backslash is refused because the driver would switch to NTLM. Statements must match the deployment allowlist byte for byte and must start with SELECT, INSERT, UPDATE, DELETE, MERGE or WITH. A T-SQL batch needs no semicolon between statements, so EXEC, EXECUTE, any sp_ or xp_ procedure, OPENQUERY, OPENROWSET, OPENDATASOURCE, BULK, WAITFOR and the DDL, permission, transaction and administrative keywords are refused anywhere in a statement.

SQL Server has no session read-only setting that the adapter could use. A query capability runs inside a transaction that is always rolled back, so a write that reaches the server is undone; sequence values, identity increments and other non-transactional effects are not undone. The adapter does not set ApplicationIntent=ReadOnly. That intent does not make a primary replica or a standalone server read-only. It only matters in an availability group: through a listener it asks for a read-only routing redirect, which the adapter refuses; a primary set to ALLOW_CONNECTIONS = READ_WRITE rejects it; and a secondary set to ALLOW_CONNECTIONS = READ_ONLY admits only read-intent connections, so the adapter cannot reach such a secondary. A secondary set to ALL accepts the adapter and serves its databases for read access only. Read-only therefore rests on the login's grants and the statement checks, with the rollback as a backstop. The adapter was tested against SQL Server 2022.

DB_HOST, DB_NAME and TABLE_NAME are placeholders. Microsoft SQL Server listens on TCP 1433 by default (a default instance uses TCP 1433, while named instances use dynamic ports unless an administrator fixes one); substitute the real host, port and database in the endpoint, the egress allowlist and the resource locator together.

Read operations are registered at R0, inserts and updates at R2, and deletion at R3. On supported execution paths mediated by AAES Govern, delete requires approval by an authorized person; bypass and observation-only paths are outside that guarantee. The SQL connector's method vocabulary is query or exec, not HTTP methods. A capability named row.insert is a promise about the statement the deployment allowlist will permit, not a check this file makes. Every capability touches one table resource classified pii as a starting point; a deployment whose table holds no personal data may lower it, and one holding payment or health data must raise it.

Least privilege lives in the database, not in this pack: db_datareader grants SELECT on the whole database and db_datawriter grants INSERT, UPDATE and DELETE on the whole database, which is broader than one table; prefer object-level GRANT SELECT, INSERT, UPDATE or DELETE on the one table for the capabilities you enable. Review the login's grants and the statement allowlist before enabling any write.

AAES has not been certified by the database vendor; the endpoints here are configuration to review and test, and the vendor has not endorsed it.