SQL Server Native Client must be installation way?-CodePudding

SQL Server Native Client pb12.5.2 + sqlserver2008, the Client must be installation way? Direct copy the SQL Server Native Client DLL in the program path can deny? Which a few DLL can?

CodePudding user response:

Convenient: connect the oledb database
With the original concept runtime packager to package support DLL, or, the share directory of all of the DLL directly to kao to the program directory

CodePudding user response:

reference 1st floor SBKS response:

save trouble: connect the oledb database
With the original concept runtime packager to package support DLL, or, the share directory of all of the DLL kao to directly to the program directory

The share directory of all of the DLL kao to the program directory.

Can use oledb connection, what's the difference between OLDEB link connected with SNC?

CodePudding user response:

refer to the second floor WellSoft response:

Quote: refer to 1st floor SBKS response:

Convenient: connect the oledb database
With the original concept runtime packager to package support DLL, or, the share directory of all of the DLL kao to directly to the program directory

The share directory of all of the DLL kao to the program directory.

Can use oledb connection, what's the difference between OLDEB link connected with SNC?

Oledb driver has been built in the Windows operating system, don't you go to install
I understand the wrong you mean, thought is pb DLL, such as SNC dedicated driver, had better be in complete drivers installed on the client, simply copy the driver DLL generally difficult to have the effect

CodePudding user response:

reference SBKS reply: 3/f

Quote: refer to the second floor WellSoft response:

Quote: refer to 1st floor SBKS response:

Convenient: connect the oledb database
With the original concept runtime packager to package support DLL, or, the share directory of all of the DLL kao to directly to the program directory

The share directory of all of the DLL kao to the program directory.

Can use oledb connection, what's the difference between OLDEB link connected with SNC?

Oledb driver has been built in the Windows operating system, don't you go to install
I understand the wrong you mean, thought is pb DLL, such as SNC dedicated driver, had better be in complete drivers installed on the client, simply copy the driver DLL generally difficult to effective

Oh, it's convenient for think so can only use the OLEDB, but don't know what is the difference between with SNC.

CodePudding user response:

reference 4 floor WellSoft response:

Quote: reference SBKS reply: 3/f

Quote: refer to the second floor WellSoft response:

Quote: refer to 1st floor SBKS response:

Convenient: connect the oledb database
With the original concept runtime packager to package support DLL, or, the share directory of all of the DLL kao to directly to the program directory

The share directory of all of the DLL kao to the program directory.

Can use oledb connection, what's the difference between OLDEB link connected with SNC?

Oledb driver has been built in the Windows operating system, don't you go to install
I understand the wrong you mean, thought is pb DLL, such as SNC dedicated driver, had better be in complete drivers installed on the client, simply copy the driver DLL generally difficult to effective

Oh, it's convenient for think so can only use the OLEDB, but don't know what is the difference between with SNC.

Don't suggest you use the OLEDB
I have two kinds of methods are
In the case of large data operations
OLE DB experience poor
The SNC way worse than not a packet
SNC, after all, is a dedicated interface optimization is better than the OLEDB this built-in common interface

CodePudding user response:

That means each Client can only install a SQL Server Native Client.

CodePudding user response:

Top, high version proposal is essentially the client

CodePudding user response:

I feel from the OLEDB to SNC for many years, SNC good ~

CodePudding user response:

Actually the best measured by oneself

Today have time to test yourself, share a set of test data, for your reference,
Database sqlserver2005, test table test1
The CREATE TABLE test1 (
Id int primary key,
The name varchar (20),
Image image,
Dt datetime,
Num int,
Price, numeric (10, 2),
Des nvarchar (Max)
)

Data volume article 10 w
Pb9
Odbc essentially a native client10.0 drive, retrieve 422 ms
SQLOLEDB drive, retrieval ms 1016
SNC way in, no more
Pb12.5
Odbc essentially a native client10.0 drive, retrieve 500 ms
SQLOLEDB drive, retrieve 16219 ms (note that didn't write wrong more than 16 seconds, tested many times, I also shocked)
SNC drive retrieval takes 454 ms

You can test under our

CodePudding user response:

Can help,
To upgrade to SP4 SQL2008, Client unable to connect to, no matter what outfit which SQL Server Native Client all not line, the Server reshipment SQL2008 (SP3) no, the original is SP3 is possible.

CodePudding user response:

The

references to the tenth floor WellSoft response:

master for help,
To upgrade to SP4 SQL2008, Client unable to connect to, no matter what outfit which SQL Server Native Client is not, the Server reshipment SQL2008 (SP3) no, the original is SP3.

Turned out to be yourself dizzy, don't know when to delete pbsnc125. DLL files, with respect to OK.

CodePudding user response:

Please comment:

SNC and oledb way, use the code to distinguish, what's the difference between the following two ways:
1. "the SQLCA. DBMS=" OLE DB "
2. "the SQLCA. DBMS=" SNC SQL Native Client (OLE DB)
"I in the following designated:
The SQLCA. DBParm="PROVIDER='SQLNCLI10'"

references 9 f pcwe2002 response:

is best measured by oneself

Today have time to test yourself, share a set of test data, for your reference,
Database sqlserver2005, test table test1
The CREATE TABLE test1 (
Id int primary key,
The name varchar (20),
Image image,
Dt datetime,
Num int,
Price, numeric (10, 2),
Des nvarchar (Max)
)

Data volume article 10 w
Pb9
Odbc essentially a native client10.0 drive, retrieve 422 ms
SQLOLEDB drive, retrieval ms 1016
SNC way in, no more
Pb12.5
Odbc essentially a native client10.0 drive, retrieve 500 ms
nullnullnullnullnullnullnullnullnullnullnullnull