|
|
|
Rank: Guest
Groups:
Joined: 8/10/2009
Posts: 732
|
This is a nice utility. Thanks!
Am I right thinking that it will only connect through named pipes? I have customers who only allow TCP connections to their servers, so I can't use this in the field.
|
|
|
|
Rank: Administration
Groups: Administrators
Joined: 8/10/2009
Posts: 368
|
Guest wrote:Am I right thinking that it will only connect through named pipes?
No, TCP/IP works just fine. Whatever you are able to connect through SSMS, you should be able to connect with this tool too
|
|
|
|
Rank: Guest
Groups:
Joined: 8/10/2009
Posts: 732
|
You're right - I'm connecting fine now with TCP, with a slight workaround.
I found I have to specify the port number in the Connect to SQL Server dialog, e.g. "tcp:MyServer,1440", which I don't need with SSMS. It's likely there's just some issue with my SQL browser service.
Anyway, thanks for your speedy reply; it was very encouraging!
|
|
|
|
Rank: Administration
Groups: Administrators
Joined: 8/10/2009
Posts: 368
|
You are right. By default SQL Server listens on port 1443. It seems SSMS can magically connect on 1440 in your case. But in general if you use any custom port, just add it after comma at the end.
|
|
|
|
|
