Guys,
So many thanks for you kind help. I was able to find the culprit, just
adding 1 index i can get as fast as 30 thousands record per hour. So that I
can proccess 2 million data in about 4 days only.
But now, after my main tables loaded with more than 2 million data (2,9
million), i have an
bject: Re: HELP --- Slow SP
> > CREATE TABLE `his_msisdn_imei_activ_hist` (
> > `MSISDN` varchar(23) NOT NULL,
> > `ACTIV_IMEI` varchar(20) NOT NULL,
> > `ACTIV_PHONE_TYPE` varchar(100) NOT NULL,
> > `PREV_IMEI` varchar(20) default NULL,
> > `PREV_PHONE_TYPE` v
> > CREATE TABLE `his_msisdn_imei_activ_hist` (
> > `MSISDN` varchar(23) NOT NULL,
> > `ACTIV_IMEI` varchar(20) NOT NULL,
> > `ACTIV_PHONE_TYPE` varchar(100) NOT NULL,
> > `PREV_IMEI` varchar(20) default NULL,
> > `PREV_PHONE_TYPE` varchar(100) default NULL,
> > `ACTIV_TIME` datetime NOT NULL,
> >
Bennett; mysql@lists.mysql.com
Subject: Re: HELP --- Slow SP
Hi,
When I used the EXPLAIN command, i see that all of my query are using the
correct index. That's why i was quite sure that index won't be the cause of my
slow query problem.
So, i now should alter the table: remove prima
Hardi OK wrote:
Hi,
When I used the EXPLAIN command, i see that all of my query are using
the correct index. That's why i was quite sure that index won't be
the cause of my slow query problem.
So, i now should alter the table: remove primary key and recreate index?
If your queries are us
Hi,
When I used the EXPLAIN command, i see that all of my query are using the
correct index. That's why i was quite sure that index won't be the cause of
my slow query problem.
So, i now should alter the table: remove primary key and recreate index?
Many thanks,
Hardi
On 4/28/06, Daniel Kasak
Quentin Bennett wrote:
I think that you can use the left most columns of the index, without including
the remainder.
That's wasn't my understanding of how things work, but I've just checked
the documentation, and it looks like you're right:
MySQL cannot use a partial index if the colum
[snip]
Next point is that MySQL will only make use of an index in a join or a
where clause if ONLY that field is included in the index. If you pack 3
fields into an index and then try to join on ONLY ONE field, the index
can't be used. So look at your joins and where clauses and make sure
your
Hardi OK wrote:
Hi Forums,
I have a frustrating problem on my Stored Procedure. It can only proccess
about 100 records in 10 minutes. I have 2 million initial records that need
to processed. Meaning that with this speed i will around 200 days to finish
all of them.
To make it worse, the data its
