Using this OLEDB code (above) instead, it handles loading the Excel data much more reliably. Previously, Jet would fall over if my Excel file was too big. Give the code above a try, it may save you a lot of Googling, desperately trying to find back-door fixes to Jet not being supported.Īctually, this using this tactic has actually made my SQL Server stored procedure even better. excel 2007 (.xlsx) INSERT INTO MyTable SELECT FROM OPENROWSET('.12.0', 'Excel 12.0 DatabaseD:test.xlsx', Customer) excel 97-2003 (.xls. ![]() So, now, I can read data directly from Excel, without actually needing Jet to be registered or installed. If you are using 圆4 SQL server then one workaround is to install instance of 32 bit SQLExpress side by side with your SQL Server. SELECT * FROM OPENROWSET('.12.0', 'Excel 12.0 Database=C:\FileName.xls HDR=YES', 'SELECT * FROM ') had the following solution which did work for me: ![]() None of these suggestions helped me to get rid of the following error, when trying to get my SQL Server 2008 Stored Procedure access an external Excel file: GO / - Not sure commented bits are necessary but I also have run them EXEC .4.0, N.
0 Comments
Leave a Reply. |