Robert L. Stewart
rl_stewart at highstream.net
Tue Apr 24 12:22:28 CDT 2007
John, Try setting up a linked server using the text files as the server files. This would allow SQL Server to operate as if they were SQL files. Robert At 12:00 PM 4/24/2007, you wrote: >Date: Tue, 24 Apr 2007 12:07:11 -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: <004301c7868a$9e6cd590$657aa8c0 at m6805> >Content-Type: text/plain; charset="us-ascii" > >The CSV file is on the same machine. It appears that the clause that pulls >the source table (csv file) into memory is taking a ton of time. These are >large files, the smallest are a little under 200 million bytes and the >largest are up in the 3 gigabyte range. It appears that SQL Server does not >read a few records and append them, but rather reads the whole CSV and then >starts appending all of the assembled records. > >If I were a SQL Server pro I could probably speed this up considerably. >Alas, I am not. > >John W. Colby