specify network protocol (tcp, np) on QA connection

Question

specify network protocol (tcp, np) on QA connection

Jane Matheson-154829

SSCertifiable

Points: 5522
More actions
June 7, 2005 at 12:18 pm

#87742

I know this can be done, but I've misplaced the exact syntax. Can anyone help me to remember how to specify a particular connection protocol(named pipes or TCP) as part of the server name in the query analyzer connection box? It went something like this:
SQL Server: <my server> [np]|[tcp]
but obviously this isn't correct or I wouldn't be asking.

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Matthew Galbraith SSC Eights! Points: 995 More actions · Answer 1

I'm not sure about doing it in the connection dialog in QA, but you can always use SQL's Client Network Utility, found in the SQL program group, to configure an alias for the server. I've always used this method when I needed to specify the port number when using non-standard ports but you can also specify the network library to use.

Carl B. SSCertifiable Points: 7931 More actions · Answer 2

Hi Jane,

If you look in BOL you'll see that ISQLW cannot be called with a parameter stating which protocol to use. In fact the [only] parameter availlables - according to BOL - are:

isqlw

[-?] |

[

[-S server_name[\instance_name]]

[-d database]

[-E] [-U user] [-P password]

[{-i input_file} {-o output_file} [-F {U|A|O}]]

[-f file_list]

[-C configuration_file]

[-D scripts_directory]

[-T template_directory]

]

Regards,

Carl

Jane Matheson-154829 SSCertifiable Points: 5522 More actions · Answer 3

I know this can be done. I've done it before. You can specify in QA when you enter the server name the protocol to use to connect.

Carl B. SSCertifiable Points: 7931 More actions · Answer 4

Hi Jane,

On the command line when calling isqlw?

If you find it again, please post it because it is not in the documentation.

Regards,

Carl

Jane Matheson-154829 SSCertifiable Points: 5522 More actions · Answer 5

OK, called an old friend I thought had a copy of the documentation and here is the answer

instead of entering <servername> on the connection box enter:

tcp:<servername> -- tcp connection

np:<servername> -- named pipes connection

lpc:<servername> -- this is shared memory

Carl B. SSCertifiable Points: 7931 More actions · Answer 6

Carl B.

SSCertifiable

Points: 7931

June 8, 2005 at 8:51 am

#563841

Nice to learn.

Thanks,

Carl

Jane Matheson-154829 SSCertifiable Points: 5522 More actions · Answer 7

I'm not sure it works in anything but the gui conenction box in QA. Never tested anywhere else. It's a good quick way to make sure your protocols are working when you are having connection issues.

Rudyx - the Doctor SSC-Forever Points: 43695 More actions · Answer 8

Good things sometimes come in small packages - as this one goes it's a keeper !!!

RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."