When creating a system DSN via the ODBC Admistrator dialog....

What is the differecne between "SQL Native Client" and "SQL Server" drivers
listed in the "Create New Data Source" drivers list?

How do they differ?

"Coder23" <Coder23@discussions.microsoft.com> wrote in message
news:B50C82B2-70C8-4F28-89CA-248F039A048E@microsoft.com...
> When creating a system DSN via the ODBC Admistrator dialog....
>
> What is the differecne between "SQL Native Client" and "SQL
> Server" drivers
> listed in the "Create New Data Source" drivers list?
>
> How do they differ?

From MSDN:
"SQL Native Client is a data access technology that is new to
Microsoft SQL Server 2005, and it is a stand-alone data access
application programming interface (API) that is used for both OLE
DB and ODBC. It combines the SQL OLE DB provider and the SQL ODBC
driver into one native dynamic-link library (DLL) while also
providing new functionality above and beyond that supplied by the
Microsoft Data Access Components (MDAC). SQL Native Client can be
used to create new applications or enhance existing applications
that need to take advantage of new SQL Server 2005 features such
as multiple active result sets (MARS), user-defined data types
(UDT), query notifications, snapshot isolation, and XML data type
support."

- Arnie

Thanks, that helps.... but what about the other one listed? ("SQL Server"
driver)

Which is the appropriate one to use in an IIS/Website scenario in terms of
data access?


"Arnie" wrote:

> "Coder23" <Coder23@discussions.microsoft.com> wrote in message
> news:B50C82B2-70C8-4F28-89CA-248F039A048E@microsoft.com...
> > When creating a system DSN via the ODBC Admistrator dialog....
> >
> > What is the differecne between "SQL Native Client" and "SQL
> > Server" drivers
> > listed in the "Create New Data Source" drivers list?
> >
> > How do they differ?
>
> From MSDN:
> "SQL Native Client is a data access technology that is new to
> Microsoft SQL Server 2005, and it is a stand-alone data access
> application programming interface (API) that is used for both OLE
> DB and ODBC. It combines the SQL OLE DB provider and the SQL ODBC
> driver into one native dynamic-link library (DLL) while also
> providing new functionality above and beyond that supplied by the
> Microsoft Data Access Components (MDAC). SQL Native Client can be
> used to create new applications or enhance existing applications
> that need to take advantage of new SQL Server 2005 features such
> as multiple active result sets (MARS), user-defined data types
> (UDT), query notifications, snapshot isolation, and XML data type
> support."
>
> - Arnie
>
>
>

"Coder23" <Coder23@discussions.microsoft.com> wrote in message
news:A3AAA0F0-1898-4453-8D19-9613BA7FAA08@microsoft.com...
> Thanks, that helps.... but what about the other one listed?
> ("SQL Server"
> driver)
>
> Which is the appropriate one to use in an IIS/Website scenario
> in terms of
> data access?
>
The 'normal' SQL Server Driver should be fine unless you plan to
use some of the new features that were mentioned for SQL Server
2005. We use SQL Server 2000. I haven't tried to run the new
driver against it yet.

- Arnie