So let's say I were to change my convert&load program to write a batch of records to a local file, then call LOAD INTO to load it. Obviously this adds some extra disk overhead, but if LOAD INTO is fast enough, maybe it's worth it.
What would be a good size / number of records for such a batch? 1000? 10000? 100000? -steve Craig Vincent wrote: >>I have several CD's worth of records that are being converted >>and then inserted into our phone listing database. the total >>db size will be about 22 million listings. >> > >Take a look at the LOAD INTO command, it was designed specifically for mass >INSERTs and is well optimized for the procedure. > >Sincerely, > >Craig Vincent > > -- Steve Rapaport World Citizen --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
