October 23, 2002 at 11:52 am
Afternoon Everyone,
I am looking for any information on comparisons between TCP/IP connections and named pipes connections. Barring that directions to kb or whitepapers that will give me ammo for an argument I am going to have. ;-)>
I work on a project that requires secure connections both locally and remotely over citrix. I joined a few months ago. Our current app (developed in VB 6) uses named pipes to connect to the db both locally and over citrix.
I know that tcp/ip has lower overhead. The current developer's argument is that named pipes is required to allow collection of the nt user ID and workstation name for our auditing.
I know it can be done without named pipes. (Saw it on a previous project.)
As always, any help is appreciated.
Richard
Richard L. Dawson
Microsoft Sql Server DBA/Data Architect
I can like a person. People are arrogant, ignorant, idiotic, irritating and mostly just plain annoying.
October 23, 2002 at 2:01 pm
Simple way to prove your argument:
(1) on a client, configure an alias using Client Network Utility to a known server. Ensure the netlib is TCP/IP. Choose a name like OnlyViaTCP, obviously not a real server to reinforce your point.
(2) Start Profiler up on the server the alias points to. Be sure the TextData, NTUserName, NTDomainName, HostName, and LoginName are present as data columns and ensure the Audit Login event event is being monitored.
(3) Bring up Query Analyzer and connect to the SQL Server using the alias along with NT Windows authentication.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply