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

Instance Names not supported #20

Closed
thewilli opened this issue Mar 12, 2012 · 7 comments
Closed

Instance Names not supported #20

thewilli opened this issue Mar 12, 2012 · 7 comments
Assignees

Comments

@thewilli
Copy link

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.

@ghost ghost assigned pekim Mar 15, 2012
@pekim
Copy link
Collaborator

pekim commented Mar 15, 2012

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.

@pekim
Copy link
Collaborator

pekim commented Mar 18, 2012

I'm afraid that I've been working on #16 this weekend, and haven't had a chance to work on this yet.

pekim added a commit that referenced this issue Mar 18, 2012
Not yet used, other than by integration test.

Issue #20
pekim added a commit that referenced this issue Mar 18, 2012
@pekim
Copy link
Collaborator

pekim commented Mar 18, 2012

This is now supported.

The documentation has not been updated yet, but the gist of the changes are that in config.options either port or instanceName (but not both) may be specified.

So instead of something like this

var config = {
    userName: 'test',
    password: 'test',
    server: 'hostname',
    options: {
        port: 1433
    }
};

you can use something like this

var config = {
    userName: 'test',
    password: 'test',
    server: 'hostname',
    options: {
        instanceName: 'MYINSTANCENAME'
    }
};

@pekim
Copy link
Collaborator

pekim commented Apr 11, 2012

Documentation updated.

@pekim pekim closed this as completed Apr 11, 2012
@pekim
Copy link
Collaborator

pekim commented Apr 15, 2012

Included in v0.0.4.

@jpolvora
Copy link

How connect with Integrated Secuirity = true? I mean no username and no password (windows authentication)

@pekim
Copy link
Collaborator

pekim commented Feb 24, 2013

Tedious does not support Windows authentication (#68 (comment)).

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

No branches or pull requests

3 participants