Prepare SQL access#
Enable the intended SQL TCP listener and confirm its actual port. 1433 is a common default, but your installation may use another port.
Create a dedicated login with the permissions required by the supported database scripts. Avoid sharing your machine administrator or website login.
Allow the company addresses listed in Connection guide through your SQL firewall. Ask the team if no company address is listed.
Save and test#
In Connection → Database, enter the server address, port, SQL username and password. Map your catalogs, save, then select Test connection. Saving records the configuration; it does not itself prove connectivity.
For a saved connection, a blank password reuses its encrypted value only while the host, port and username stay unchanged. Changing any of those requires the SQL password again.
Network and certificate checks#
Production SQL connections use encryption. A certificate or server-name error needs the SQL certificate and operator configuration reviewed. Private destinations require a company-approved network exception; do not switch off protection to bypass an error.