Skip to content
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

Closed
wanglei8155 opened this issue Mar 1, 2021 · 4 comments · Fixed by #34
Closed

mssql 2008 connect failed #19

wanglei8155 opened this issue Mar 1, 2021 · 4 comments · Fixed by #34

Comments

@wanglei8155
Copy link

docker logs xxx
...
Failed to connect to database: Failed to connect to xxx:1433
....

@theKorzh
Copy link
Contributor

theKorzh commented Mar 3, 2021

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.

@awaragi
Copy link
Owner

awaragi commented Mar 24, 2022

I have added @theKorzh comments to FAQ section. Part of the 1.1 release. Thanks.

@awaragi awaragi linked a pull request Mar 24, 2022 that will close this issue
@astingengo007
Copy link

astingengo007 commented Apr 4, 2022

@awaragi How can I use named instance to connect like: 1.2.3.4\SKDEV1.5 and custom port 1388 [or even default one]?

@awaragi
Copy link
Owner

awaragi commented Apr 4, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants