forcing ODBC connection to use Named Pipes

Question

forcing ODBC connection to use Named Pipes

subotai

Mr or Mrs. 500

Points: 540
More actions
June 16, 2015 at 11:40 am

#147336

I am testing connectivity issues and I would like an ODBC connection to use Named Pipes, but I don't see anywhere to edit the connection string on ODBC Administrator on the client. FYI I'm using SQL Server Native Client 10 and Named Pipes is enabled on the SQL Server 2005 Network Configuration of the SQL Server configuration manager.
Forum Etiquette: How to post Reporting Services problems

[/url]

Forum Etiquette: How to post data/code on a forum to get the best help - by Jeff Moden
[/url]

How to Post Performance Problems - by Gail Shaw
[/url]

Joie Andrew One Orange Chip Points: 27360 More actions · Answer 1

If you have SQL Server Configuration Manager on the machine trying to use Named Pipes you can setup the order protocols are tried. Otherwise you can setup a SQL Server alias specifying Named Pipes be used.

One other option is if you can use a file DSN you should be able to modify the DSN file directly specifying Named Pipes.

Joie Andrew
"Since 1982"

mister.magoo SSC-Forever Points: 47068 More actions · Answer 2

Just put the prefix np: in front of the server name.

MM

select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);