You have also 3000 * 7 millions columns to left joins to x,y,.. others tables.
And you use myisam. this will certainly be a big update problem.
I suggest you to transform your query into :
1. select using the left joins to see first the number of rows to be updated
2. according to this number the strategy can be different :
small number => update
large number => tempo table containing the non updated rows
copy the "will be updated" rows to tempo
truncate table
load tempo in the main table
Mathias
Selon Emmett Bishop <[EMAIL PROTECTED]>:
> Mike,
>
> Thanks for the insight. The "sent" table has about 7
> million records. The other tables involved have tens
> of thousands of records or there abouts. Not your 100
> million size but certainly worth exploring.
>
> Thanks again,
>
> Tripp
>
> --- mos <[EMAIL PROTECTED]> wrote:
>
> > Tripp,
> > This problem may occur if your table is
> > quite large (several gb in
> > size). The update may make the table too large to
> > address using
> > conventional MySQL pointers. You may need to modify
> > the table so it has a
> > "Max Rows=nnnn" option where "nnnn" is the max rows
> > you expect the table to
> > have and this forces MySQL to use a larger table
> > pointer. When my tables
> >
> === message truncated ===
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - Find what you need with new enhanced search.
> http://info.mail.yahoo.com/mail_250
>
> --
> 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]
