A connection, clearly defined.
The right syntax for your driver.

Explicit settings.
Fewer surprises.

Choose the client that will make the connection. SqlClient and ODBC use different keywords and value quoting.

Authentication and secrets

Integrated authentication uses the application's execution identity and its database permissions; it does not use your browser sign-in. Windows clients require the appropriate identity. Linux and macOS clients typically need Kerberos configuration. SQL logins require SQL authentication to be enabled on the server.

Use a placeholder while sharing or saving examples. Including a password reveals it in the output and clipboard. This page does not store form values or send them to a server. Reset clears the entered password.

Encryption and certificates

Required encryption with certificate validation is the starting setting. The client must trust the certificate chain and the certificate must match the server name. Trusting a certificate skips validation; use only when you deliberately accept that tradeoff. Optional encryption does not guarantee an encrypted connection; server settings may still require it.

Ports, named instances and listeners

A TCP port avoids named-instance discovery. Named-instance connections may require SQL Server Browser or a client alias. For AG listeners, enable MultiSubnetFailover and use the listener endpoint. ReadOnly is a routing intent, not a permissions restriction; routing also requires server-side configuration.

Supported output

This builder supports Microsoft.Data.SqlClient and Microsoft ODBC Driver 18, using Windows or SQL authentication. It does not test connectivity or generate Entra, JDBC, LocalDB or access-token authentication. ODBC values containing a closing brace are rejected to avoid ambiguous driver parsing.