SQL Server

Configure the Connection

SQL Server 2017 and later are supported. The connector authenticates with a SQL username and password.

Connection Parameters

Omit the database name or leave it empty to use the SQL login's default database.

URI Connection Strings

Monospace accepts the following URI connection-string forms.

sqlserver://user:password@host:1433/database

mssql://user:password@host:1433/database

The database path is optional. Both forms accept the case-insensitive SQL Server keywords Encrypt and TrustServerCertificate as query parameters.

A pasted URI with no Encrypt keyword therefore uses a different default from the manually configured Studio form.

Configure Encryption

The manually configured Studio form offers three policies:

Use Verify Full for production connections across an untrusted network.

With Verify Full, upload an Additional CA Certificate when the server certificate uses a private certificate authority. The field accepts one PEM or DER CA certificate, or a PEM bundle.

The supplied certificates are accepted in addition to the default trusted roots. Those roots remain trusted, and the connector still validates the server certificate chain and hostname.

Limitations

• Some existing-field migrations are not yet supported. You cannot change a field's type or nullability, or add IDENTITY to an existing field.
• JSON uses string storage. SQL Server 2025's native JSON data type is not yet supported. Monospace stores JSON in NVARCHAR(MAX), so values can be read and written. But equality compares serialized text rather than JSON structure, so equivalent objects with different key ordering do not match.
• Composite primary keys containing IDENTITY prevent creates. A collection whose composite primary or unique key contains an IDENTITY field does not offer create operations.
• Large updates and deletes have an item ceiling. updateMany and deleteMany can fail when an operation matches roughly 2,000 items with a one-field primary or unique key. Updates also need parameters for changed values, so their practical ceiling is lower. Composite keys reduce the approximate item ceiling in proportion to their field count. For larger mutations, page through key values and send bounded updates or deletes. Separate mutations do not preserve the atomicity of one operation.

See Also

• Connectors — every way to connect a data source
• Introspection — how Monospace discovers a database schema
• Data Types — how field values appear in API requests and responses
• Schema Migrations — change collections, fields, indexes, and relations