Skip to content
datasquares.aiSign inStart free

Connect DataDatabases

SQL Server

You connect SQL Server from the DataSquares connection wizard.

  1. In DataSquares, open Data Sources and choose Connect Source. The Connect a data source page opens.

  2. Pick SQL Server on that page (search or browse by category).

  3. Fill in the connection details below, then test the connection and save.

Field What to enter
Host The hostname or IP address of your SQL Server server.
Port Prefilled with 1433 (the SQL Server default) — change it if your server listens elsewhere.
Database The database to connect to.
Username / Password Credentials for a user with read access to the tables you want to analyze.
TLS On by default: Use SSL/TLS encryption connects encrypted and verifies the server certificate. Tick Trust self-signed certificate for a private CA; turn TLS off only for a server that has none.

Grant the connection user read-only access — DataSquares only ever reads from your source.

CREATE LOGIN datasquares WITH PASSWORD = '********';
USE analytics;
CREATE USER datasquares FOR LOGIN datasquares;
ALTER ROLE db_datareader ADD MEMBER datasquares;

The form takes a host and port — for a named instance, find its TCP port (SQL Server Configuration Manager → your instance → TCP/IP) rather than using HOST\INSTANCE syntax, and make sure TCP/IP is enabled. Default instances listen on 1433.

Test Connection shows a short summary, such as Authentication failed — check the username and password. The text below is what the database itself reports, for example in the SQL editor.

Error Cause / fix
Login failed for user SQL authentication must be enabled (Mixed Mode) — Windows-only auth rejects SQL logins
certificate errors on connect the server uses a self-signed certificate — turn on Use SSL/TLS encryption and Trust self-signed certificate (only for a server you control); for production, install a CA-signed certificate
Server did not negotiate encryption Use SSL/TLS encryption is on and the server offers none: it has no TLS. DataSquares stops before it sends the login, so the password never crosses the network unencrypted. Install a certificate on the server, or turn Use SSL/TLS encryption off for this source (its login and data then cross unencrypted). Test Connection reports it as Secure connection failed — check the SSL/TLS settings.
timeout port blocked, TCP/IP disabled on the instance, or SQL Browser needed for a named instance