Hi Ken..

this might not solve your problem..
but, did you really have to do this

create table raddata (
 granID                    integer not null,
 scanID                    tinyint unsigned not null,
 fpID                      tinyint not null,
 c1                        smallint,
 c2                        smallint,
 c3                        smallint,
      [and so on and so forth....]
 c2376                     smallint,
 c2377                     smallint,
 c2378                     smallint,
 primary key (fpID, scanID, granID)
);

just looking your table definition, i can imagine how long it will
take to insert data..
couldnt you break it down to two table??
like 

create table raddata (
 granID                    integer not null,
 scanID                    tinyint unsigned not null,
 fpID                      tinyint not null,
 primary key (fpID, scanID, granID)
);

create table radcolumns (
 granID                    integer not null,
 scanID                    tinyint unsigned not null,
 fpID                      tinyint not null,
 cID                       smallint,
 cValue                 smallint,
 key (fpID, scanID, granID)
);

maybe this can help....


On Thu, 26 Aug 2004 08:11:53 +1000, Daniel Kasak
<[EMAIL PROTECTED]> wrote:
> Ken Gieselman wrote:
> 
> >Hi Folks --
> >
> >I'm running into some issues with large prepared statements, and would love some
> >feedback about approaches or tweaks that I might have overlooked :)
> >
> >
> >
> >
> <snipped>
> 
> >Any suggestions as to how to do this more efficiently/faster?  Or how to
> >increase the buffer space for the prepared statements, so as to do the inserts
> >in larger groups?
> >
> >
> I can't comment on prepared statements - I've never used them. I'm
> running a 4.0.x server here.
> But I do know that one of the fastest ways to get data into MySQL is
> with 'load data infile'.
> Maybe you export your data to a csv file and import it that way? Line up
> each 1000 inserts in a text file and then run 'load data infile' or
> something like that?
> 
> It's not the cleanest solution, granted, but if you need to to work
> better in a hurry, this might be your ticket ( at least until you figure
> out what's up with your prepared statements ).
> 
> --
> Daniel Kasak
> IT Developer
> NUS Consulting Group
> Level 5, 77 Pacific Highway
> North Sydney, NSW, Australia 2060
> T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
> email: [EMAIL PROTECTED]
> website: http://www.nusconsulting.com.au
> 
> 
> 
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]
>

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to