Thanks for the tip, the unc address worked for me. But being new to SSIS (only in chapter 3) this makes me wonder if any input file I need for my package will need to be moved into a subfolder of the package itself vs. some common area of the network? Or can it be on another server and just use the unc address there in the connection manager? I've been able to send output flat files to my local C drive (and other servers) from the SSIS server so this source connection wrinkle is a little puzzling. Maybe this is just a peculiarity of the bulk insert task, I haven't tried other tasks that use a file input. The connection manager itself validated my local path when I created it so this just happened at runtime.
|