Post reply

Comparison of TCP/IP and Named Pipes?

  • May 7, 2005 at 6:38 pm

    #68988

    When it comes to connecting to your SQL Server from you client, what is the difference between using a Named Pipe and a TCP/IP connection?

  • May 9, 2005 at 7:36 am

    #557583

    Hello Vanessa,

    Look in BOL (books online) you'll see many topics about that subject. It depends on how deep you want to go but if you search for these keywords in BOL you will find relatively good doc about it: TCP/IP, NAMED PIPES, Network protocols, communication components.

    Regards,

    Carl

  • May 9, 2005 at 1:17 pm

    #557692

    Named Pipes is a Microsoft network protocol. TCP/IP is the standard used on the internet. Non-MS networks need to have it installed in order to communicate with SQL Server. TCP/IP is universal.

    However, if you are using Windows Server 2000 and TCP/IP along with Kerebos security and having trouble maintaining a connection MS recomends that you use named pipes instead of TCP/IP.

    I don't think there is much difference performance wise. Using Named Pipes means you don't have to worry about maintaining DNS names and addresses.

  • May 9, 2005 at 1:28 pm

    #557694

    Just to add a little more complexity, you can use Named Pipes but the underlying protocole stack is TCP/IP.

    Carl

Viewing 4 posts - 1 through 3 (of 3 total)

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