Viewing 15 posts - 1 through 15 (of 33 total)
OPENROWSET works amazingly well as long as you are not operating on 64bit platform.
Example:
INSERT INTO {some table} ({field list})
SELECT {field list} FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
...
July 9, 2009 at 6:21 am
If your procedure uses table variables in complex joins, that can do it.
August 29, 2007 at 5:09 am
I use this feature frequently but my syntax looks like:
SELECT * FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0','Excel 8.0;IMEX=1;Database=D:\Book1.xls;',...
February 23, 2007 at 12:22 pm
Wow! I have been looking for a download page like that for a long time. Very helpful, indeed. Thanks.
February 23, 2007 at 9:05 am
Thanks for you input. I did run regedit to modify MSDTC settings but the behavior did not change. I must note that I could not configure exactly like the KB article. The Oracle server...
February 23, 2007 at 7:59 am
Thanks for the reply. The second article sounded particularly useful so I set all the parameters as specified. However, it didn't help. Neither article specifically mentions INSERTing from a stored...
February 21, 2007 at 1:21 pm
If you rely on linked servers for distributed queries, get ready for a potentially bumpy ride. Especially if you want to use Windows-only (Kerberos) security. Also, the Microsoft Oracle provider does not...
February 9, 2007 at 5:19 am
Also, you can create a linked server using the Jet OLE DB provider.
And new to SQL 2005, the OPENROWSET function with BULK option is very cool.
January 26, 2007 at 6:51 am
Agreed. I have a very similar problem and am working with MS Product Support but no solution yet.
I wonder if your have same behavior. I can create the linked...
January 3, 2007 at 9:54 am
Avoid table variables for complex joins or large data sets. SQL Server does not compute statistics for them, hence, can not determine an adequate execution plan. SQL 2005 is even...
December 19, 2006 at 7:08 am
Thanks for the effort, but, so far, nothing helps. My understanding is that MS has not ported the Jet and ODBC providers to the 64-bit environment and that's that. I...
December 14, 2006 at 8:42 am
Using the IMEX=1 option overcomes the problem (if it is a problem) of SQL Server engine trying to determine data type and size. It can lead to real problems if...
September 19, 2006 at 6:58 am
I started off installing Oracle's 10G 64bit OLEDB driver but could not figure out how to make it work for linking purposes and I could not find any info in...
July 11, 2006 at 7:26 am
Thanks John. That is pretty much as I suspected. It looks like I'll have to run my queries through the 32-bit server for the time being.
Because we rely so heavily on...
July 11, 2006 at 7:13 am
Ditto that. I have the same problem with a couple of linked Oracle servers we use for distributed queries. Care to elaborate on the workaround?
July 11, 2006 at 6:48 am
Viewing 15 posts - 1 through 15 (of 33 total)