SQL Server
Connect a Microsoft SQL Server database for federated analysis. Tables are mounted into the query engine and can be joined with datasets from other connectors.
When to use
- Microsoft SQL Server instances used as application backends or reporting stores.
- Azure SQL Database and SQL Managed Instance, where reachable, connect through the same fields.
For sustained analytical load, prefer a read-only replica or a reporting secondary.
Before you begin
Prepare a login with:
- Read-only privileges on the target database (for example membership in
db_datareader). - Network connectivity from Datyo to the instance. If it is in a private network, allow inbound access or expose a reachable endpoint.
Connection settings
| Field | Required | Description |
|---|---|---|
| Host | Yes | Server hostname or address, e.g. sqlserver.example.com. |
| Port | Yes | Default 1433. |
| User | Yes | Login name. A read-only login is recommended. |
| Password | Yes | Stored encrypted; never shown after saving. |
| Database | Yes | The database to connect. |
| Encrypt | — | Whether to negotiate an encrypted connection. Enable it when the server requires encryption. |
Test and save
Select the type, enter the fields, and use Test connection. On success the dataset saves and moves through "syncing → connected". After connecting, choose the tables to import.
Capabilities
- Execution model: Federated. SQL Server tables can be joined with datasets from other connectors.
- Access: Read-only. Write statements are rejected.
Troubleshooting
- Test connection fails — verify host and port, login and password, and that the database name is correct.
- Encryption errors — toggle Encrypt to match the server's requirement; some instances mandate an encrypted channel.
- A table is missing — confirm the login can read it (for example via
db_datareader).
Improve answer accuracy
- Add column descriptions for business fields.
- Re-sync after a schema change.