Thanks for the input, Patrick. Installing the native SQL client is not an issue as we have enterprise licenses for SQL 2005, 2008 R2, and 2012. The only drawback I see of using the native SQL driver is ensuring the user has it installed. So that means we have to include instructions in our installation guides for the user to ensure the driver is installed on their computer before running the database.
Darrell
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of pwood57@gmail.com
Sent: Thursday, February 06, 2014 2:31 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] RE: Native ODBC Versus MDAC ODBC Driver
Hi Darrell,
Here is important info about MDAC from a Microsoft MSDN article entitled "Data Access Technologies Road Map"
http://msdn.microsoft.com/en-us/library/ms810810.aspx
"SQLODBC: The Microsoft SQL Server ODBC Driver (SQLODBC), which supports access to Microsoft SQL Server, has been deprecated. Its connectivity to future versions of SQL Server may not be supported. The ability to connect to versions earlier than SQL Server 7 will be removed from the operating system after Windows 7. New applications should use the SQL Server Native Client ODBC driver (or the successor to the SQL Server Native Client ODBC driver, the Microsoft ODBC Driver for SQL Server on Windows), which supports new SQL Server features. Existing applications should migrate to the SQL Server Native Client ODBC driver as well for better performance, reliability and supportability (see Updating an Application to SQL Server Native Client from MDAC for more information)."
A very important issue is continued support for ADODB. Microsoft advises us to use SQL Server Native Client for the present. The problem is that when support for SQL Server 2012 ends so will support for OLEDB which ADO requires to work.
With SQL Native Client you still have support for ODBC linked tables in SQL Server.
If I remember correctly Microsoft no longer includes SQL Server Native Client with Office so you may need to install it although if you have install one of the latest editions of SQL Server such as SQL Server express or the SQL Server tools you should already have it.
For earlier versions:
You will need to click "Install instructions" and install "Microsoft® SQL Server® 2012 Native Client" which is about half way down the page.
MSDASQL, the 64-bit OLEDB Provider for ODBC, still works for ADO the last time I checked and is still available although it is old technology that has not been improved in years. MSDASQL is said to be not a fast as SQL Server Native Client but you may not notice a difference depending upon your network.
Patrick Wood
---In MS_Access_Professionals@yahoogroups.com, <DEmbrey@...> wrote:
Greetings All,
Do any of you have any thoughts you could share on the subject of using a native ODBC driver versus using the MDAC ODBC drivers? Long ago, I was taught to use a native driver, if one was available. Being a good, obedient Airman, I did as my supervisor told me without question. Fast forward now to my civilian life and I brought up this philosophy in a discussion with my supervisor today. She made the subject one of my objectives for this year to write a technical document on the advantages and disadvantages of using native ODBC driver versus a generic ODBC driver.
I did find one blog article on MSDN but not much else. If anyone can provide any other references on the subject, I would appreciate it.
Darrell
The information contained in this communication is highly confidential and is intended solely for the use of the individual(s) to whom this communication is directed. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information is prohibited. Please notify the sender, by electronic mail or telephone, of any unintended receipt and delete the original message without making any copies.
Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are nonprofit corporations and independent licensees of the Blue Cross and Blue Shield Association.
The information contained in this communication is highly confidential and is intended solely for the use of the individual(s) to whom this communication is directed. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information is prohibited. Please notify the sender, by electronic mail or telephone, of any unintended receipt and delete the original message without making any copies.
Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are nonprofit corporations and independent licensees of the Blue Cross and Blue Shield Association.
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (3) |
Tidak ada komentar:
Posting Komentar