jwcolby
jwcolby at colbyconsulting.com
Fri Mar 30 07:25:52 CDT 2012
BCP works fine when you already have a table definition. Without that it is problematic. This file was 250 GB in size. The first line was a header definition but getting at that was almost impossible. I did manage to use the built-in import wizard, jiggle a couple of the field sizes and then just let it run. It took overnight but it worked. The database is now in. >> A quick look in BOL should give you everything you need to know. This has to be my favorite saying of all times. Learning anything from BOL is like trying to learn French by intentionally moving in with a crusty old french farmer in the boonies of the alps. You probably will learn French eventually but there are about a billion easier ways. John W. Colby Colby Consulting Reality is what refuses to go away when you do not believe in it On 3/30/2012 4:10 AM, Mark Breen wrote: > Hello John, > > On the basis that it was you that thought me BCP in 1998, I guess you have > considered it. > > However, I am curious, are you already using it and if not, it is not > practical or convenient to use it? > > Mark > > > On 26 March 2012 17:50, Arthur Fuller<fuller.artful at gmail.com> wrote: > >> JC, >> >> You might be able to speed up the import dramatically by using bcp (the >> bulk copy utility that comes with SQL Server). I have used it to import >> many millions of rows and it's lightning-fast, compared to other tools. >> >> A quick look in BOL should give you everything you need to know. >> HTH, >> A. >> -- >> AccessD mailing list >> AccessD at databaseadvisors.com >> http://databaseadvisors.com/mailman/listinfo/accessd >> Website: http://www.databaseadvisors.com >>