Viewing 15 posts - 16 through 30 (of 33 total)
I have a similar situation and avoid using DTS or SSIS by first BULK INSERTing the text file into a temp table with one very wide column. Then I SELECT...
March 20, 2006 at 9:01 am
That's what I meant to convey. This morning I tried to apply the Jet driver update but it failed because I already have the most recent version--which was applied with...
March 16, 2006 at 11:47 am
No spaces in UNC path.
A KB article indicated that version of MDAC was the culprit, specifically, the Jet4.0 component. I tried to update according to the article but the installation...
March 16, 2006 at 9:16 am
I tried what you said but I get the same result. I set SQLAgent's proxy account to the same domain service account as the MSSQLService, but no change. This service...
March 16, 2006 at 7:05 am
It turns out that all the techniques (Linked Server, OPENDATASOURCE, and OPENROWSET) work just fine with UNCs on my SQL Server 2005 test machine. I read a KB article that...
March 15, 2006 at 1:56 pm
Yep, that's correct. And SQL Server Service is running under a special domain account that has been given explicit permissions to the share.
March 15, 2006 at 11:30 am
Yes. There are no special restrictions placed on the workbook or share. And I do not have this problem with other t-sql operations.
cjb
March 15, 2006 at 9:45 am
Unfortunately, I have the same problem with OPENDATASOURCE. It works great as long as the spreadsheet is local...kind of sounds like a share Permissions issue, perhaps.
cjb
March 15, 2006 at 9:17 am
Hmmmm...didn't think of the OPENDATASOURCE thing. And it probably doesn't require a Named Range, either. I will definitely try it out.
Thanks, Allen.
March 15, 2006 at 8:34 am
Yet another approach is to write to a table, then use sp_OA... stored procedure to create a BulkCopy object and "export" the table to a file. I got this method...
February 7, 2006 at 9:52 am
I agree that it is too bad that you did not include bcp and DTS in your analysis. For a simple write to file, though, DTS seems hardly appropriate. And when...
February 7, 2006 at 6:45 am
Yes, thank you. That was the problem.
I reconfigured to use Windows Authentication instead of sa. Didn't think to look for that.
Thanks!
August 25, 2005 at 7:47 am
That's OK; thanks for trying. I am just as puzzled.
August 24, 2005 at 12:51 pm
The service account is a domain account. Nevertheless, I tried a different domain account (in sys admin role) as well as a local administrator account. Nothing works.
cjb
August 24, 2005 at 12:42 pm
No, just the run-of-the-mill SQL Server sa account.
I even set the password back to what it was prior to the change but that has not helped.
cjb
August 24, 2005 at 12:14 pm
Viewing 15 posts - 16 through 30 (of 33 total)