October 18, 2010 at 11:45 am
I'm loading a delimited text file into SQL Server. Simple Data Flow task with a File Source and a SQL Server Destination. When I debug this task, SQL Server is doing something weird. It's skipping past the Source (no highlighted color at all) and going straight to the destination with the error:
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "Could not bulk load because SSIS file mapping object 'Global\DTSQLIMPORT ' could not be opened. Operating system error code 2(The system cannot find the file specified.). Make sure you are accessing a local server via Windows security.".
Now I'm running this against our QC server, but doing it in BIDS local to my desktop. So, I'm obviously violating the tail end of this error message. I usually use OLE DB Destinations and have never seen this behavior before, but now I'm working on a package created by another DBA.
Can someone tell me why would SSIS skip the Source and go straight to the Destination? Is this behavior normal for the SQL Server Destination?
October 19, 2010 at 12:41 pm
You can only use SQL Server Destination if the destination is on the same server.
This BOl article explains why:
http://msdn.microsoft.com/en-us/library/ms141095.aspx
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
October 20, 2010 at 4:49 am
But if you aren't on the same server, does SSIS always skip past the Source and go straight to the Destination during Debug?
Or am I just seeing strange behavior?
October 20, 2010 at 4:53 am
I guess SSIS does some validation first before it starts running and that this validation fails. You can see in the output window in what stadium the package threw an error.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply