-
Notifications
You must be signed in to change notification settings - Fork 436
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
Instance Names not supported #20
Comments
It looks like the ports for all instances can be obtained with a UDP request to port 1434. This relies on SQL Server Browser running. If it's not, the port for an instance name will not be obtainable. I will probably implement the lookup at the weekend. A workaround, until the lookup is implemented, is to configure the instances to run on specific ports and connect based on the port instead of an instance name. |
I'm afraid that I've been working on #16 this weekend, and haven't had a chance to work on this yet. |
Not yet used, other than by integration test. Issue #20
This is now supported. The documentation has not been updated yet, but the gist of the changes are that in So instead of something like this
you can use something like this
|
Documentation updated. |
Included in v0.0.4. |
How connect with Integrated Secuirity = true? I mean no username and no password (windows authentication) |
Tedious does not support Windows authentication (#68 (comment)). |
I can connect to the server "myServer", but a connection to a named server instance (e.g. "myServer\SQLExpress") results in a "connection failed" error.
The text was updated successfully, but these errors were encountered: