Sql-server – Native SQL Server connection vs ODBC

odbcsql server

What is the difference between native SQL Server connection and ODBC? What are the benefits when using native SQL Server connection?

Best Answer

When possible, you should always use Sql Native Client, or the Native Sql Data Provider. It is far more superior in terms of performance than an ODBC connection.

ODBC is basically another layer of abstraction. It might be interesting if you want to support different databases and to switch them at run-time, but if you're sure you're going to stick with Sql Server, Native Client is the way to go.

Related Solutions

Sql-server – How to get this SQL Server ODBC Connection working

Named pipes and TCIP protocols for SQL server 2005 are disabled by default. Have you enabled them under "SQL server configuration manager"? You can find the protocols in the SQL Server Network configuration and under SQL Native client xx configuration.

The connection on the server itself works thanks to the "Shared memory" protocol.

Sql-server – SQL Server ODBC Connection via Command Line

The SQLCMD utility will probably be your best option. From what you've indicated it meets all of the requirements above: command-line, ODBC driver, SQL Authentication. The basic syntax would be something like:

sqlcmd -S <servername> -U <login>

see: sqlcmd Utility

This should work fine in Windows XP but unless you've got SQL already installed on the client machines you will need to manually install SQLCMD and the SQL Native Client. Downloads for distributable packages for both of these can be found here.

Best Answer

Related Solutions

Sql-server – How to get this SQL Server ODBC Connection working

Sql-server – SQL Server ODBC Connection via Command Line

Related Topic