dbexpress TCP/IP and Named Pipes
Posted: Wed 11 Oct 2006 08:55
I would like someone to explain how dbExpress communicates with the SQL-server and wich settings affects the connection. I thougth that the SQL-client tha comes on the SQL2000-server disk does not affect the connection.
In our application we use the property "OS Authentication=True".
Our application used to use BDE and back then we had to install the SQL-client and the BDE. Now we don´t have to install the SQL-client anymore, still there are some clients that have the SQL-client installed. These clients have Named pipes as their primary protocol in the "SQL Server Client Network Utility", all these clients get named pipes as their connection type to the SQL-server. If they set TCP/IP as their primary protocol the connection turns into TCP/IP. If a client doesn´t have the SQL-client installed they get TCP/IP as their connection type.
But if our developers have the named pipes as their primary protocol and login to the database, they get TCP/IP as their connection typ.
I hope some can clear this out
In our application we use the property "OS Authentication=True".
Our application used to use BDE and back then we had to install the SQL-client and the BDE. Now we don´t have to install the SQL-client anymore, still there are some clients that have the SQL-client installed. These clients have Named pipes as their primary protocol in the "SQL Server Client Network Utility", all these clients get named pipes as their connection type to the SQL-server. If they set TCP/IP as their primary protocol the connection turns into TCP/IP. If a client doesn´t have the SQL-client installed they get TCP/IP as their connection type.
But if our developers have the named pipes as their primary protocol and login to the database, they get TCP/IP as their connection typ.
I hope some can clear this out