I would always choose TCP/IP over Named Pipes. It is far more manageable.



Mangual Janet A. (WASD) wrote:

>Hello Guru's:
>
>
>
>SQL server contains definitions of all aliases for every instance on the
>server. Some defined to use named pipes others TCP/IP. When trying to
>register from a client machine, got error that registration failed. Do we
>need to have each definition also on each client pc that will access any of
>the instances\db? Let' say we will have several hundreds of users accessing
>the server in addition to the developers. Any way to accomplish this task
>without impacting the user?
>
>
>
>Any recommendations between which network library to use TCP/IP or Named
>pipes and Why?
>
>
>
>Janet Mangual
> <http://www.miamidade.gov/> www.miamidade.gov
>
>"Delivering Excellence Every Day"
>Miami-Dade County is a public entity subject to Chapter 119 of the Florida
>Statutes concerning public records. E-mail messages are covered under such
>laws and thus subject to disclosure
>
>
>
>
>
>---------------------------------------------------------------------
>TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
>Website : http://www.LazyDBA.com
>To unsubscribe: http://www.lazydba.com/unsubscribe.html
>
>
>.
>
>
>

MS Sql Server LazyDBA home page