sql server native client 2008R2

Question

HI

1.What should I see in the "Add or Remove programs" after I had installed the sql server 2008 R2 native client.

2.How should I determine that i have to install a 32 bit or a 64 bit native client for a 32 bit application. Should the bit count normally corresponds to the bit count of the application.

3. After installing the native client , what should see under the "Drivers" Tab in  the 32 bit  ODBC administrator console.

Regards

Answer 1

You should install the version coresponding to the operating system it runs on (e.g. x86 / x64)

Below is on 64 bit 2008 R2 server

 

 

 

 

 

 

---

Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]

Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Answer 2

so you mean that the choice of the native client (32 bit or  64 bit) depends upon the OS and not the application.

In my case the workstation upon which the native client and the application is to be installed is windows 7 64 bit. So i belive i have to install native client which is 64 bit.Also I heard that one has to use the %systemdrive%\Windows\SysWoW64\ odbcad32.exe directory for the ODBC administrator console incase of a 32 bit application. Is it right? The database server is a dedicated machine and  is a sql server 2008 R2 .

Regards

Answer 3

Yes, that's correct.

http://msdn.microsoft.com/en-us/library/ms131321(v=sql.105).aspx

Yes, use %systemdrive%\Windows\SysWoW64\odbcad32.exe for 32 bit data source and %systemdrive%\Windows\System32\odbcad32.exe for 64 bit data source.

 

 

 

---

Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]

Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Answer 4

Thanks dave.

I appreciate.

I had installed the native client and the third party application.

This application created automatically ODBC profiles which can be seen in ODBC console presented by %systemdrive%\Windows\SysWoW64\ odbcad32.exe directory.

But while configuring the correct profile intended for this third party application and the database server. Error message pops up.

 The setup routines for the SQL Server ODBC driver could not be found.  Please reinstall the driver."

This is followed by a dialog titled: "Driver's ConfigDSN, ConfigDriver, or ConfigTranslator failed."  The body text of the dialog is "Component not found in the registry."

The driver correct on i.e. sql server native client 10 is already there in the drivers tab. but why I am getting this error.

I have seen this question already but i dont think it would help.

P.S.  Would  it help to reinstall the native client.

Answer 5

Does the Test Connection work? This may be a question for the application developer.

 

 

 

---

Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]

Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Answer 6

iThe issue is riving me crazy.

 The communication to the database server using management studio is ok.

The communication to the database server by manually adding the odbc profile works ok as well.

But the odbc profile i.e. system dsn which gets created automatically after installation has to be configured so that application can communicate to the database server.

The application developer has told that this automatically created profile has to be used but as i told while configuration, the error message pops up as in the last message.

There is one thing which might be causing issue. The system DSN which the application developer has told to configure has the sql server native client infront of the name.And I cannot understand that, can the installation of a third party application could install the sql server native client driver?This driver i.e sql server native client i believe could cause the issue since this driver cannot be used with sql server 2008R2 database server . Am I correct?

However I could see the correct driver i.e sql server native client 10 in the drivers tab of odbc administrator console.

Regards