64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003
We’re pleased to announce that 64-bit MSDASQL for Windows Server 2003 is now available for download at https://www.microsoft.com/downloads/details.aspx?FamilyID=000364db-5e8b-44a8-b9be-ca44d18b059b. This update will also be available through “Windows Update” soon.
What is MSDASQL?
MSDASQL is an OLEDB/ODBC ‘bridge’ that allows applications built on OLEDB and ADO (which uses OLEDB internally) to access data sources through ODBC drivers. MSDASQL ships with the Windows Operating System, and Windows Server 2008 and Windows Vista SP1 are the first Windows releases to include a 64-bit version of MSDASQL.
Isn’t MSDASQL Deprecated?
Previous messaging on MSDN indicated that a 64-bit version of MSDASQL would not be available. However, we have received numerous requests from customers for this technology and we are making it available on the following Windows operating systems: Windows Server 2003, Windows Vista SP1 and Windows Server 2008. Microsoft has no plan yet to deprecate this technology currently.
Mo Lin
Program Manager, Data Programmability
Comments
Anonymous
April 07, 2008
PingBack from http://lostdriveblog.com/2008/04/07/64-bit-oledb-provider-for-odbc-msdasql-is-now-available-for/Anonymous
April 07, 2008
4 апреля 2008г. стала доступна для загрузки 64-разрядная версия MSDASQL для Windows 2003/XP. ПоставщикAnonymous
April 16, 2008
Does this now mean that 64 bit SQL Server can access .MDB data files through a linked server. I have already built a kludge using a 32 bit named instance to remedy this severe compatibility problem in 64 bit SQL Server, but would be happy to be able to accomplish the same task in a cleaner way.Anonymous
April 24, 2008
Now that I have access to the ODBC drivers (thanks), how do I get the "Microsoft Text Driver (*.txt, *.csv)" amongst the other drivers installed on my x64 server?Anonymous
April 26, 2008
In case you've been waiting for this (even if you thought MSDASQL was being deprecated), it'sAnonymous
April 28, 2008
I'm trying to create a linked server to a SQL server (localhost - just for testing). When I create a DSN using the regular ODBC link (in system32) it works. However, when I create the DSN using the c:WINDOWSSysWOW64odbcad32.exe it does not work. Any Ideas? ThanksAnonymous
April 30, 2008
I am also experiencing the same issue. Loaded the new 64-bit MSDASQL, but it does not see the 32-bit ODBC DSN created on the Server. The environment is Server 2003 (64) & SQL Server Enterprise 2005 Clustered (64). My ultimate goal is to create a Linked Server to our Informix database. We done this successfully on our 32-bit SQL Server Standard 2005 environment. Unfortunately, IBM doesn't have a 64-bit ODBC driver for Informix.Anonymous
May 05, 2008
The following codes works well on windows xp 32-bit but fails on windows xp 64-bit, I have installed the 64-bit msdasql, anybody can help me? Thanks! _bstr_t strConnect="Provider=MSDASQL;Driver={Microsoft Access Driver (*.mdb)};Dbq=C:/test/test.mdb;"; m_pConnection.CreateInstance("ADODB.Connection"); hr =m_pConnection->Open(strConnect,"","",NULL);Anonymous
May 09, 2008
The MSDASQL provider only bridges OLE DB to ODBC. It does not bridge 64-bit to 32-bit. This means that 32-bit OLE DB Providers, such as Jet, and 32-bit ODBC Drivers, such as the text driver, are still inaccessible to SQL Server 64-bit. In addition, since the Microsoft Access ODBC driver is not thread-safe, and the text driver is based on this, using these drivers from SQL Server or IIS is not supported. You would have to use the OLE DB connection string for these and these are limited to being called from 32-bit applications only.Anonymous
June 15, 2008
I ported the OpenCSV project (opencsv.sourceforge.net) to the .NET Framework. This version is read-only, although if you want a writer, let me know. Unlike OpenCSV, OpenCSV# returns a datatable, so you can simply pass in a CSV filename and it will be parsed and returned in a form that's bindable! You can download the DLL and the source at: http://aurigroup.com/downloads/OpenCSVSharp.zip So why not use the Microsoft Text Driver? Well, Microsoft's Text Driver doesn't work on Microsoft's 64-bit operating systems! Necessity is the mother of all invention, and therefore I'm releasing my port of OpenCSV for all .NET users to enjoy :) Also unlike OpenCSV, OpenCSV# support setting whether the first row of data is the column headers, and automatically populates the column names so you don't have to work with index values and potentially wrong data. Technical details:Written in C# instead of Java.
Written for .NET Framework 2.0 and above.
Made the ParseLine() function public so you can just pass a string and parse it, in case you don't want to parse an entire file. I haven't tested the ParseLine direct call, fyi. Enjoy! Auri Rahimzadeh President, The Auri Group, LLC (TAG, www.aurigroup.com) Contributor, ASP.NET Pro Magazine, Consultants Corner (yep, I do that column) Author, Hacking the PSP, Geek My Ride Technical Editor, Building Web Sites Bible 3rd Edition, Beginning Access 2007 VBA
Anonymous
July 29, 2008
Has any user had any success with this? It hasn't fixed my problem. I'm not sure the install file works. I can't find any evidence of a new msdasql dll on my system. What is the file name and date? where is it installed? A rock solid ASP application with about 50 installations will not connect to SQL Server on Windows Server 2003 64 bit.Anonymous
August 05, 2008
I've had no success either. I've created system dsn's in both the 64bit and 32 bit sections... I've installed the patch, reboted... every random thing I can think of, and I still get the exact same error. My connection strings look like this DSN=DATABASE_someDB; Initial Catalog=someDB;user id=someUser;password=somePassword Still getting the exact same no default provider message. I can get it to work if I change my connection string... but that's the whole point... I've got a ton of websites using just a few dsn connections... specifically so I wouldn't have to change them all if I moved to a new server etc. ArghhhhAnonymous
August 05, 2008
actually... after doing a little more research, I've discovered something that might be a mind bogglingly simple solution... given, it still involves a slight alteration to the connection string, but still uses the dsn... Same connection string as above but you add a provider to the front getting rid of the infamous (no default provider) message Provider=MSDASQL; DSN=DATABASE_someDB; Initial Catalog=someDB;user id=someUser;password=somePassword It's also probably worth mentioning that my dsn's connect to sqlserver, but just adding that provider description did the trick. it was this article that clued me in... http://www.asp101.com/articles/john/connstring/default.asp Enjoy hopefully that will help someone.Anonymous
August 08, 2008
Does this mean that my SSIS package running on Windows Server 2003 Enterprise 64 bit would now be able to read Excel files? We are having to run the package in 32 bit mode because it was not possible to use it in 64 bit.Anonymous
August 18, 2008
Más de una vez me lo han preguntado y he aquí una solución: http://ssis.trigonblue.com/Excelin64bitenvAnonymous
August 18, 2008
Hi, How 32-bit applications could use a 32-bit version of .UDL files? Is there a 32-bit OLEDB subsystem under Windows 64-bit as there is for ODBC? For ODBC we have: %windir%SysWOW64odbcad32.exe %windir%system32odbcad32.exe For OLE DB we normally use UDL files, which seems to use only 64-bit OLE DB Drivers. Thanks.Anonymous
August 18, 2008
I just found how to do it: http://blogs.msdn.com/chaitanya_medikonduri/archive/2008/04/09/how-to-run-32-bit-udl-file-on-a-64-bit-operating-system.aspx Here is the 32-bit version of OLEDB subsystem: Program Files (x86)Common FilesSystemOle DBoledb32.dllAnonymous
August 18, 2008
When will Microsoft provide both a 64-bit ODBC driver and OLEDB Provider for Jet, Excel and Text files?Anonymous
October 08, 2008
Any suggestions how to make an x64 application read an excel file when jet is not supported.Anonymous
January 25, 2009
Also wondering when a 64-bit ODBC driver for Windows x64 will be made available? Have searched far and wide and none to be found. How can that be, and, when will one be made available? Would love to make use of 64-bit PERL, but, without the drivers, no can do....Anonymous
February 18, 2009
Dears, Is there any provider on windows server 2008 (64-bit)to read an Excel File ?? Please help me!!!Anonymous
February 26, 2009
The comment has been removedAnonymous
June 19, 2009
Thought this idea might be of some help. I'm trying to access a MS Access 2003 file while on a Win2003 64 bit system. I was able to use the 32 bit providers when I ran Powershell in 32 bit mode. (%SystemRoot%syswow64WindowsPowerShellv1.0powershell.exe) I use the connection string from here: http://skatterbrainz.blogspot.com/2009/05/using-powershell-with-ms-access.htmlAnonymous
October 28, 2009
Microsoft is planning to release 64 bit version of office i.e office2010 to have both 32 bit and 64 bit flavors. once its released we should have 64 bit drivers as well. this should resolve most of the 64bit driver issues with excel,jet etcAnonymous
February 08, 2010
I have installed the 64bit msdasql on windows server 2003 and can't seem to figure out how to create a linked server for importing excel into sql. In vb.net i would do: Dim odbbcconnectionstring As String = _ "Driver={Microsoft Excel Driver (*.xls)};" & _ "DBQ=" & FileToConvert & ";" Dim odbcconn As New Odbc.OdbcConnection(odbbcconnectionstring) Dim odbcCmd As New Odbc.OdbcCommand("SELECT * FROM [Sheet1$]", odbcconn) but not even sure how to do it with the 64 bit driver. Can someone provide assistance on the openrowset query pointing to the 64 bit driver to load excel into sql. thanks!Anonymous
May 13, 2010
Hi, Does these Jet Oledb drivers works On 64 bit Win 2008 server as well.Because i searched MSDN,it says these drivers are availiable for 32 bi server only? Does anyone have any ideas how to achieve this? Regards, AmitAnonymous
May 13, 2010
Hi, Does these Jet Oledb drivers works On 64 bit Win 2008 server as well.Because i searched MSDN,it says these drivers are availiable for 64 bit server on Win2003 only? Does anyone have any ideas how to achieve this? Regards, AmitAnonymous
August 05, 2010
This was asked before, but I'll be specific, I'd downloaded and run the setup for this bridge on a 2003 x64 server. I go to open the ODBC administrator for 64 bit drivers and I still only see SQL Server. The appliction I am running requires a DSN value, not a connection string, so can the ODBC administrator for 64 bit be used to create a DSN. How do I get this ODBC driver listed?Anonymous
April 19, 2011
You mentioned that a x64 bit version of MSDASQL will be available for a number of OS? Is Windows XP one of those?Anonymous
August 11, 2011
Does it has solve this problem The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine on windows server 2003 64 bit