November 2, 2012 at 4:59 am
Hi all, is there anyone out ther, who fixed this issue?
November 4, 2012 at 6:38 pm
bjoepe (11/2/2012)
Hi all, is there anyone out ther, who fixed this issue?
I've solved it before. In my case I was running SQL Server 2008 R2 64 bit and 32 bit version of MS Office. With the 32 bit version of Office installed, I could only install the 32 bit version of the ACE OLE DB provider. That mismatch (64 bit SQL and 32 bit Office) cause the error.
In my case, I uninstalled the 32 bit office and installed 64 bit Office (including the 64 bit ACE OLE DB provider) and the issue went away.
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
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply