Re: Connection issues with ADO

On Sat, 28 May 2005 10:58:40 -0700, Frank Rizzo <nospam@xxxxxxxxxx>
wrote:
in <eq5kf66YFHA.3096@xxxxxxxxxxxxxxxxxxxx>

>Hello,
>
>I distribute an app to various folks that allows them to connect to
>various SQL Servers. I have no control over what version of ADO they
>have installed, but it's version 2.5 or higher.
>
>With ADO 2.5 the default connection protocol was named pipes. With ADO
>2.6, they've changed the default to TCP/IP.
>
>When users try to connect using ADO 2.5, sometimes the connection fails
>for varoius reasons: the user is not on the domain and the server they
>are connecting to is or they are connecting across non-trusted domains
>and so forth.
>
>So my questions are as follows:
>
>1. Will it have any repercussions if I force the connection to TCP/IP,
>by appending "Network Library=dbmssocn" to the connection string? Will
>I still be able to connect to the local machine regardless of ADO version?
>
>2. Named pipes work fine as long as you are authenticated on the
>domain. Is this a correct assumption?
>
>3. I can always use Named Pipes to connect to my local sql server. Is
>this correct?
>
>4. What about if the user's PC and the SQL Server are in the same
>workgroup. Will named pipes still work?
>
>Thanks

Named pipes will not work with any 9x based system, so your assertions
are correct if all clients/servers are NT based systems. You could
always ~encourage~ your clients to upgrade to MDAC 2.8 the way MS
~encourages~ upgrades. Use your imagination here.


---
Stefan Berglund
.

Relevant Pages

  • Re: Sql Server 2000 slow
    ... If I close the connection (moving the Open/Close ... ADO) and the dll gives twice the performance. ... > Are there any known performance issues with .NET accessing Sql Server ...
    (microsoft.public.dotnet.framework.performance)
  • RE: [ODBC SQL Server Driver][Shared Memory]ConnectionWrite (send()
    ... remote connection. ... should I just check named pipes only or both TCP/IP and ... I understand that you encountered the ODBC error message on your ecommerce ... TCP/IP protocol to your SQL Server instance by calling conn.Open, ...
    (microsoft.public.sqlserver.connect)
  • Connection issues with ADO
    ... I have no control over what version of ADO they have installed, but it's version 2.5 or higher. ... When users try to connect using ADO 2.5, sometimes the connection fails for varoius reasons: the user is not on the domain and the server they are connecting to is or they are connecting across non-trusted domains and so forth. ... Named pipes work fine as long as you are authenticated on the domain. ... What about if the user's PC and the SQL Server are in the same workgroup. ...
    (microsoft.public.vb.general.discussion)
  • Re: CoInitialize failure with many processes
    ... I could not find a good reference about ADO connection pooling, ... its own connection to the SQL Server. ... Regarding the Performance Monitor, I haven't seen anything out of the ...
    (microsoft.public.win32.programmer.ole)
  • Re: netbios and named pipes sql replication.
    ... Once the client switched to named pipes, ... > connection with. ... > When we took named pipes support off the SQL server with the MS patch, ... > We had to manually walk thru the ODBC setup and configure the CLIENT ...
    (microsoft.public.sqlserver.replication)