.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

SQL Native Client for 2005

Posted By:      Posted Date: September 28, 2010    Points: 0   Category :Sql Server


I need to have on some clients the SQL Native Client driver for ODBC links. I remember that it is downloadable as a free install. Where can I find this download, please? Do I download the driver with the same service pack respect of the SQL Server on the db server? If SQL Server is to 64 bit, do I download SQL Native client to 64 bit?


View Complete Post

More Related Resource Links

SQL-DMO Install on SQL Server 2005 Express Client

I am installing a Client side SQL 2005 Express that needs SQL-DMO. The Client computer does not have SQL Server 2005 Express installed. I have installed all the MDAC and .Net 2.0. The command line I'm using to try and install the SQL-DMO and XML modules is: SQLEXPR_ADV ADDLOCAL=Tools_Legacy,SQLXML I get a message something like 'SQL Server 2005 Version does not support this install option.' How do I get SQL-DMO installed on a SQL Server 2005 Express Client computer?

Install SQL Server2005 Error:[Native Client]Encryption not supported on the client

Product: Microsoft SQL Server 2005 -- Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

Unable to connect to SQL Server 2005 remotly, all client protocols are blank

I have an installation of SQL 2005 and had issues connecting remotly. Looking at the client protocolols, they are all blank. I can see that TCPIP, Named Pipes, VIA, etc. are 'enabled', but where the words 'TCPIP', 'Names Pipes', etc. should be, it's just blank. I tried to install SQL 2008R hoping the Client Protocols would be corrected during the installaion, but they were not. I'm assuming the issue with the Client Protocols not showing up is a symptom of the problem. Does anyone have any ideas? Thanks!

SQL Server allowing access with NATIVE CLIENT Protocols are disabled.

I have disabled all client protocols from SQL Server Configuration Manager -> Sql Native Client configuration -> Client Protocols.Still I am able to access sql server with all client protocols disabled. Why ?Also I stopped the SQL Server Services and restarted it again. Then also the system is allowing me to connect with all the client protocol disabled.

Where is SQL Native Client 10.5.xxxx for Visio 2010

When attempting to use Reverse Engineer tool in Visio 2010 Professional for the Database Model Diagram, selecting SQL Native Client as the data source provider only gives the ODBC SQL Server Native Client as 10.0 (SQL Server 2008). How do I use 10.5.xxxx to connect to a SQL Server 2008 R2 database. Obviously the 10.0.xxxx provider won't understand the newer data types available in 2008 R2.

SQL Server 2005 Express - Does it require a Client Access License (CAL)

Do you need a Client Access License (CAL) for each device that will connect to a SQL Server 2005 Express edition database?

SQL Server Native Client is substitute of WDAC (MDAC)?

Forking this subquestion from my question Does SQL Server clients use (WDAC, MDAC) and when? Having read msdn article  SQL Server 2008 R2 Native Client Programming I could not understand: Is SQL Server Native Client (SSNC) intended to be used as advanced substitute for MDAC (currently renamed as WDAC)? what one could have understood from th? article... Except that this article tells: "The SQL Server Native Client ODBC driver is always used in conjunction with the ODBC Driver Manager supplied with Windows DAC" From one side it sounds that SQL Server Native Client (SSNC) provide the same functionalities that MDAC (WDAC) and more being "a stand-alone data access API,". From the other side, it is written that SSNC is dependent on MDAC(WDAC) components (drivers, dll) and vice versa. So, why 2 parallel, having essentially the same functionalities, data access structure duplicates?

Can not connect to SQL 2005 Instances from Client

Dear Experts I have a problem. I am not able to connect to Remote SQL Server instances from my PC. Though some of my team members are able to connect to the Instances without any problem. We have tried with all the below options and no joy. 1. We tried connecting, with the IP Address, like IP\<ServerInstance>, Port# 2. Added the IP address to Host file with the network address and tried, like <WINServerName>.<networkaddress>\<ServerInstance>, Port#, even without the Port#. 3. Tried to create an ODBC DSN, why this because, this had resolved the issue some times. Thought will help, but didn't work out. After all these, whenever we tried to connect to the server, we received the below error message. Error Message : Can not connect to <WINSERVER>.NetworkAddress\<DBInstance> A network-related or instance-specific error occured while establishing a connection to SQL Server. The server was not found or was not  accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (Provider :TCP Provider, error:0 - No such Host is known) (Microsoft SQL Server, Error - 11001). Kindly help to resolve this issue. I have been strugling since quite some time. Regard Deepak

MS Access ADP projects need to be able to use SQL Native Client

Microsoft, PLEASE update the Access ADP platform to be able to connect to SQL Server 2005 using the SQL Native Client.  ADP is a great in-house development platform, but MS seems to have decided to stop supporting it.The problem is, the sql ole db driver that the ADP projects use, cause problems when querying complicated views or stored procedures on SQL Server 2005.  Queries that worked great under SQL Server 2000, time out under 2005.  When run directly on the server, there is no problem.  When they are run from the ADP file, the execution plan of the query is totally messed up.  I watched what SQL Server 2005 does with tracing, it's running certain segments of the query over and over.If I run that same query in Access, through an ADO connection, where I specify the Native Client as the provider, then I don't have that problem, which proves that the problem is the old SQL OLE DB driver. So we need the project's default connection needs to be work properly with SQL Server 2005.

SQL 2005 native driver and IDENTITY_INSERT

Greetings, We have a VB6 program using ODBC to  execute a couple of simple statements that turns the IDENTITY_INSERT ON for a table, inserts data, then turns IDENTITY_INSERT OFF. The code has executed without problems using the SQL Server driver that comes with Windows 2000/XP.  However when we set up an ODBC connection using SQL Server 2005 Native Driver, the IDENTITY_INSERT ON executes without error but the insert statement crashes with the error "Cannot insert explicit value for identity column in table 'TableName' when IDENTITY_INSERT is set to OFF" Does the SQL Server 2005 Native Driver handle this command differently?  And if so how can we get it to execute correctly?

SQL Server Native Client install fails during prerequisites

Hi I'm trying to install sharepoint 2010 on a new windows 2k8r2 which is a member server on our domain. The server is fully updated. The SQL Server native client installation fails. This is the entry in the error log;   2010-09-15 08:57:26 - Beginning download of Microsoft SQL Server 2008 Native Client 2010-09-15 08:57:26 - http://go.microsoft.com/fwlink/?LinkID=160387 2010-09-15 08:57:28 - Size of download of "Microsoft SQL Server 2008 Native Client" in bytes is "8073728" 2010-09-15 08:57:28 - Download of "Microsoft SQL Server 2008 Native Client" completed successfully 2010-09-15 08:57:28 - Installing Microsoft SQL Server 2008 Native Client 2010-09-15 08:57:28 - "C:\Windows\system32\msiexec.exe" /i "C:\Users\myadmin\AppData\Local\Temp\SQLCF11.tmp.msi" /quiet /norestart 2010-09-15 08:57:28 - Install process returned (0X660=1632) 2010-09-15 08:57:28 - [In HRESULT format] (0X80070660=-2147023264)   If I run the SQL native client installer manually I get the following error; The installer has encountered an unexpected error. The error code is 2755. Server returned unexpected error 1632 attempting to install package.   Any ideas why this is happening? I've had a quick google and can't see anything for SQL Native Client for that error code. Thanks   Olly

Should I move ODBC Apps from the SQL Server driviver to SQL Server Native Client 10.0

I have a suite of applications written for SQL Server 2000 in Access 2000 and Access 2007 and running under Access 2007 (12.0.6423,1000 SP2 MSO 12.0.6425.1000) via ODBC with the SQL Server ODBC driver (2000.85.1132.00) under Windows XP Professional (2002 SP3).  I have maintained all the data modules in Access 2000 format so that they can be accessed by SQL Server 2008 if required and am gradully upgrading the data modules to SQL Server.  The server they are connected to is Microsoft SQL Server Standard Edition (10.0.2531.0 running on a 32-bit Wndows Server 2008 Standard (SP2).  As a security improvement I intend to move a number of the applications to the server itself.  My choice of driver for ODBC is between SQL Server (6.00.6002.18005) and SQL Server Native Client 10.0 (2007.100.2531.00).  I have yet to discover any differences in application behavior or performance between the two interfaces My assumption is that I will have have fewer problems if I configure the ODBC links using the SQL Server driver.  However, I was wondering if there is a reason to gradually move them over to the SQL Server Native Client 10.0 driver. Thanks, Harry

How to insert SQL2008 date data type using ADODB.Recordset and Native Client?



I am working with a classic ASP application that we are trying to keep hobbling along while it gets rewritten.  The underlying database has been upgraded many times and is currently running on SQL Server 2008.

Recently a column of table was updated from a smalldatetime (with a check constraint to ensure it didn't have any time values) to simply the date type, but the code now does not work.  I was originally using SQLOLEDB, and was confident that treating the date as a string would be find with our client.  Unfortunately it does not, nor does it work using the SQLNCLI10 client.

This is the stripped down code:

Set adoConnection = aspServer.CreateObject("ADODB.Connection")
adoConnection.Open "Provider=SQLNCLI10"  ' Details Removed
Set adoRS = aspServer.CreateObject("ADODB.Recordset")
adoRS.CursorLocation = adUseClient
adoRS.Open "SELECT * FROM TestTable WHERE id = 0", adoConnection, adOpenKeyset, adLockOptimistic, adCmdText
adoRS("datecolumn") = "09/20/2010"

On the update line, I get the following error:

Microsoft SQL Server Native Client 10.0 error '80040e07'
Error convertin

Can I run Sql server 2000 client tools and SQL server 2005 on teh same machine.



Could you please advise me on this issue.

I have installed sql server 2000 client tools, and complete set up of sql server 2005 on my system.

The enterprise manager on sql 2000, crashes and and window vanishes, when ever i try to create DTS package.

They doubt its becos i am runnning both instance of sql server on the same machine- So its having some compactability issues.?

Can we run SQL server 2000, 2005 and 2008 on same machine with different instance ?

I am using windows 7 and i3 processor.

Thanks in advance.



SQL Native Client 10.0 for installation failed because product not supported on this operating syste



I am trying to install sql native client 10.0 on a users desktop.  I am running sql server 2008 express sp1.  She has windows vista business installed on her machine.

I have done this many times, but for some reason when I try to install sql native client 10.0 on her machine, I receive an error that states "Installation of this product failed because it is not supported on this operating system.  For more information on supported configurations, see the product documentation."

Any insight as to what could be the problem, is greatly appreciated.


M. Wilson


sql native client problem for logon CR problem



As i have developed my asp.net application with crystal report using sql server 2005.... on windows xp OS machine x86

My hosting provider is using sql server 2008 on windows server 2008 OS x64...

Please let me know the sql native client version of ms sql server 2005
and sql native client version of ms sql server 2008

will sql native client version of ms sql server 2005 will work on sql native client version of ms sql server 2008..

or we need the same sql native client version of ms sql server 2005 to run my crystal report

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend