[AccessD] using a saved SSIS with VB.Net

John,

One of the keys to getting it into SQL Server faster
is to have the CSV file on the server and not on a different
machine. Network traffic can kill the process and slow it
down significantly.

Robert

At 10:22 AM 4/24/2007, you wrote:
>Date: Tue, 24 Apr 2007 10:32:44 -0400
>From: "JWColby" <jwcolby at colbyconsulting.com>
>Subject: Re: [AccessD] using a saved SSIS with VB.Net
>To: "'Access Developers discussion and problem solving'"
>         <accessd at databaseadvisors.com>
>Message-ID: <003101c7867d$6cce93a0$657aa8c0 at m6805>
>Content-Type: text/plain;       charset="us-ascii"
>
>Gustav,
>
>My bigger issue here is that there 56 of these files to import into SQL
>Server, supposedly ~100 million records.  I have done about 8 million
>records so far.  I really must get this thing automated such that it just
>chunks through these CSV files without my having to be around to start the
>next one.  I am working now on setting up the append query using that syntax
>below into a stored procedure so that I can then just replace the file name.
>After that I will need to write something in VB.Net or whatever to execute
>the stored procedure feeding in all of the file names from a specific
>directory, deleting the file once the stored procedure finishes the import
>for a given file.
>
>I have never written a stored procedure.
>Obviously, given the above, I have never called a stored procedure from
>code.
>
>So much to learn, so little time.
>
>Once this is imported I have to turn right around and export a subset of
>fields from the table back out as 1 - 2 million record chunks for CAS / DPV
>/ NCOA processing, then I have to import THOSE back in to a new table.
>
>And when this set of data is finished, I have another set of about the same
>size on the way, to which I have to perform the same processes.  I soooooo
>need to get this process automated.
>
>John W. Colby