-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mssql 2008 connect failed #19
Comments
Probably your SQL Server is working as named instance. For named instances the TCP port is dynamically configured by default, so you may need do explicitly specify port in MSSQL settings as described here. |
I have added @theKorzh comments to FAQ section. Part of the 1.1 release. Thanks. |
@awaragi How can I use named instance to connect like: 1.2.3.4\SKDEV1.5 and custom port 1388 [or even default one]? |
Given the library I use for connectivity to mssql servers, only tcpip connections are possible. There are environment variables that allows you to specify the host name and port to connect to. See the https://github.com/awaragi/prometheus-mssql-exporter#environment-variables section about those environment variables. |
docker logs xxx
...
Failed to connect to database: Failed to connect to xxx:1433
....
The text was updated successfully, but these errors were encountered: