Windows Authentication
If you're using Windows Authentication to connect to your database currently, you'll need to set up "mixed mode" authentication. See the docs from Microsoft here.
Error codes
The error codes you receive will depend not only on the information you provide, but also your own particular infrastructure (i.e., type of database, whether you're behind a firewall, etc.). We've tried to provide explanations of he most common error codes we see customers face, but if you don't see yours here, feel free to ping us in the in-product chat, or book some time and we'd be happy to help you get connected!
There are some tips for using MSSQL for Mac at the bottom of the article.
You can also see this Microsoft MSSQL connection troubleshooting tool for a nicely branched troubleshooting process.
Common Errors
ETIMEOUT
Double check your Database Type and Port. We often see the two are mismatched in these situations. The default port for MSSQL Server is 1433.
Are you using Windows Authentication? If so, make sure the database type is set to 'MSSQL WA'.
If you have the ability to check your connection using another editor or IDE and the same authentication credentials, that can rule out access issues. If you are able to connect, please contact us in the in-product chat to continue trouble-shooting. If not, or you don't have access to another editor, continue with the steps below.
Is the database online? Using MS SQL Server Management Studio, change the code.var config = { server: "149.xxx.xx.x", database: "master",...etc. } to use the master database as your default. Then run:
select name, user_access_desc, state_desc from sys.databases where name='yourDatabase'
to see if yourDatabase is connected.
5. Does the user have access? From MS SQL Server Management Studio, run:
select * from yourDB.sys.database_principals where name = 'YourUserName'
to ensure the user has access. If no rows are returned, create the user and give them the proper permissions.
6. Do you have access to your database from the IP address you are currently using? If your database is behind a firewall, you may need to whitelist your IP address. While you're at it, consider whitelisting SeekWell's static IP address as well, as that will be necessary to set an automated schedule.
For more details, see the comments here.
ESOCKET
Double check your Database Type and Port. We often see the two are mismatched in these situations. The default port for MSSQL Server is 1433.
Are you using Windows Authentication? If so, make sure the database type is set to 'MSSQL WA'.
Is TCP/IP protocal enabled? Check and enable in "Sql Server Configuration Manager"->"SQL Server Network Configuration"->" Protocols for "->"TCP/IP"
Follow steps 3 to 6 under ETIMEOUT above
ELOGIN
There is a problem with the username or password. Double-check the credentials, then either contact your database administrator to have your username/password added or reset, or follow steps 3-6 under ETIMEOUT above.
EENCRYPT
If your database uses a Secure Sockets Layer, check the "SSL" box and try again. If you use an SSH tunnel to access your database remotely, see here for details.
MSSQL tips for Mac
Are you currently connecting to SQL Server using a virtual machine? Are you using SQL Server Management Studio to connect (it's not available for Mac, so if you are, it must be a virtual machine)?
If so, the IP address for your virtual machine is different than your Mac. You can either add your Mac's IP address to the whitelist (recommended) or download the SeekWell Windows app on your virtual machine.
General SQL Server Tips
SQL Sever on AWS
Again, please feel free to contact us if you're having trouble connecting! We can usually get you connected in a matter of minutes, and helping you helps us better understand how to write guides like this! Chat from within the product, email us at contact@seekwell.io or grab 15 minutes here.