Re: SQL Server 2008 bulk load error
- From: Blake <blake.duffey@xxxxxxxxx>
- Date: Mon, 11 May 2009 16:38:57 -0400
I appreciate your input. I am going to simply try to copy the raw data to a system that is a member of domain A - and eliminate the security context issues completely.
:)
Tibor Karaszi wrote:
I see. Thanks for the detailed explanation (needed for me since I don't have "trust issues" up to date). You didn't say what SQL command that your user is executing, but I going to assume BULK INSERT or INSERT with subselect haing OPENROWSET and the bulk provider. The point is to understand whether it is the SQL Server service which is accessing the file or something else (like Agent - if you are using a scheduled job and integration services; for example). Say that it *is* SQL Server that is accessing the file, then if the user in question has sysadmin SQL Server priviliges, then the service account is attempted. This sees to fit with what you are seeing. One thing that *might* be helpful is using Proxies and Credentials (see CREATE CREDENTIAL and Books Online index "proxy accounts [SQL Server Agent]"). I'm not entirely certain it will help, though since a) the user might be sysadmin and in that case the case *might* be that we'll habe no impersonation and b) your domain and trust setup (but here my Windows/Ad copetence starts failing me)..
- References:
- SQL Server 2008 bulk load error
- From: Blake
- Re: SQL Server 2008 bulk load error
- From: Tibor Karaszi
- Re: SQL Server 2008 bulk load error
- From: Blake
- Re: SQL Server 2008 bulk load error
- From: Tibor Karaszi
- SQL Server 2008 bulk load error
- Prev by Date: Re: SQL Server 2008 bulk load error
- Next by Date: Re: SQL Server 2008 bulk load error
- Previous by thread: Re: SQL Server 2008 bulk load error
- Next by thread: Re: SQL Server 2008 bulk load error
- Index(es):
Relevant Pages
|