Ensure that you have the .12.0 by viewing (Within your SQL DB) Server Objects > Linked Servers > Providers. To use the .12.0 provider, utilize the following commands/steps.ġ. This involved several steps, but proved to be a reliable solution once completed. I resolved this by using the .12.0 provider when connecting to Excel 2016 files using SQL script. xlsx file in my SQL script, I ran into several errors when using the providers/methods listed above. Traditionally when connecting to an Excel file within a SQL script, I utilized the OPENROWSET function in conjunction with .4.0, MSDASQL, or some other provider. The 32-bit OLE DB provider ".4.0" cannot be loaded in-process on a 64-bit SQL Server.OLE DB provider ".12.0" for linked server "(null)" returned message "Unspecified error”. Resolves the following errors when connecting to an Excel 2016 file in SQL: Hopefully this will help anyone that has run into issues with the OPENROWSET function or anyone that wants to connect to an Excel file in their SQL script, but that does not know how to do so.Ĭonnecting to Excel 2016 Files in Your SQL Script After a bit of research and experimentation, I put together the following documentation for a solution: I recently experienced an issue when trying to access an Excel file in a SQL query that I was writing on my Dynamics CRM server using the OPENROWSET function.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |