RE: query tuning

2012-11-15 Thread Iñigo Medina
That should decline significantly. What's the value of key_buffer_size? It should generally be 20% of _available_ RAM (for MyISAM usage). -Original Message- From: James W. McNeely [mailto:jmcne...@nwrads.com] Sent: Wednesday, November 14, 2012 3:48 PM To: mysql@lists.mysql.com Subject: Re

Re: query tuning

2012-11-15 Thread James W. McNeely
> Note the huge estimated number of rows. That should decline significantly. > > What's the value of key_buffer_size? It should generally be 20% of > _available_ RAM (for MyISAM usage). > >> -Original Message- >> From: James W. McNeely [mail

RE: query tuning

2012-11-14 Thread Rick James
#x27;s the value of key_buffer_size? It should generally be 20% of _available_ RAM (for MyISAM usage). > -Original Message- > From: James W. McNeely [mailto:jmcne...@nwrads.com] > Sent: Wednesday, November 14, 2012 3:48 PM > To: mysql@lists.mysql.com > Subject: Re: query

Re: query tuning

2012-11-14 Thread James W. McNeely
Rick, Thanks! Here is the create table info. Sorry for the size, but you can skip down from all the fields to see the indexes. CREATE TABLE `exams` ( `zAddDate` date DEFAULT NULL, `zModDate` date DEFAULT NULL, `IdPatient` varchar(32) DEFAULT NULL, `zModBy` varchar(255) DEFAULT NULL, `N

RE: query tuning

2012-11-14 Thread Rick James
Can't help without the SHOW CREATE TABLEs. Perhaps e needs one of these: INDEX(zzk) INDEX(ProcModeCode, dateexam) -- in that order (I can't predict which index it would use.) Are IdAppt the same datatype and collation in each table? > -Original Message- > From: James W. McNeely [mailto: