Hi All,

When using the Bulk Import cocmponent in an SSIS package, I have found
that doing a bulk import, other than locally to a database on that
instance of SQL Server, fails. So following is a more detailed
description:

Example #1: (fails)

Server A has:
1. SSIS installed
2. The files to Bulk Insert
3. The package specifies the Server A path to the bulk import data
files.

Server B has:
1. The destination database

Step 1: I create a package on Server A which Bulk Inserts a csv file
into a table on Server B.
Step 2: Run package.
Result: File system error - cannot find file specified.

Example #2: (fails)

Server A has:
1. SSIS installed

Server B has:
1. The files to Bulk Insert (I tried this because I thought maybe it
was just using the same functionality as bcp)
2. The package specifies a path that is available on Server B

Step 1: I create a package on Server A which Bulk Inserts a csv file
into a table on Server B. (The path specifies somemthing that would be
accessable to Server B.)
Step 2: Run package.
Result: File system error - cannot find file specified. (The path will
be correct, etc.)

Example #3: (succeeds)
Server A has:
(unused)

Server B has:
1. SSIS installed
2. Use the same package from example #1.
3. Bulk import files located on same exact path from example #1 on
Server A.

Step 1: Reuse package from example #1.
Step 2: Copy the bulk import files to the same literal path as was used
in example #1.
Step 3: Run package.
Result: Success.

So from this relatively simple example it seems pretty straightforward.
SSIS does _not_ support doing a Bulk Import to a remote SQL instance.
Can anyone confirm or deny this? Microsoft? I have seen other
similiar posts in this group, but nothing that confirms it in the SP1
version of 2005.

Thanks,

David Baldauff