April 25, 2013 at 9:56 am
Kudos to Lowell for revealing the secret to using the command line to force installation of the 64-bit ACE driver on a machine with 32-bit Office apps. I ran into that wall a couple weeks ago and gave up fighting it - Lowell's solution solved my problem, so I can now run openrowset queries against Excel files. Thanks!
February 21, 2014 at 6:58 am
Where can i check which driver is installed on a particular machine?
Thanks
Martin
May 7, 2014 at 9:19 pm
An old thread to be sure, but I'm trying to get this to work now with Office 2013.
I found there's a new Access Database Engine for Office 2013.
http://www.microsoft.com/en-us/download/details.aspx?id=39358
If I have the time (and remember) I'll post back once I get this working again.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St
May 8, 2014 at 12:04 am
Now here's a bit of a sticky wicket. I installed the new 2013 Access Run Time engine and my OPENROWSET query still wasn't working.
Got to poking around and found that the Microsoft.ACE.OLEDB.12.0 provider is not in my SQL 2008 Providers list but it is in the Providers for SQL 2012 (I have 2 versions of SQL Server co-existing on this machine).
Now I need to figure out how to get it in both places. I'm hoping there's a secret parameter or something on this new Access Engine installer (like /passive as Lowell found), but so far I've had no luck finding it.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St
July 8, 2015 at 9:42 am
Many Thanks that passive stuff saved my ***!!
muchas gracias hijos de puta!! me salvaron la vida conchatumareeee!!! soy seco!
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply