Marc, Remember that, while an index speeds finding the row to delete, it also slows the updating or deleting of a row. For each row that is deleted, pointers have to be removed from the index, and the previous rows and next row pointers of two other rows have to be changed to point around the deleted row.
And when you are fiddling with the order of conditions in your WHERE clause and with parenthesis, you should SET MANOPT ON, so that the query optimizer doesn't continue to try to guess its own way to be fast, but uses your suggestions instead. Bill On Wed, Jul 14, 2010 at 5:06 PM, MDRD <[email protected]> wrote: > but, I made the Index on all 3 columns using the Design mode? > Then Unloaded the structure, cut and pasted the Index code. > > So maybe you can't Index varchars form the R>? > > I think it is due to sun spots and solar activity! > > Marc > > > -------------------------------------------------- > From: "Albert Berry" <[email protected]> > Sent: Wednesday, July 14, 2010 3:43 PM > To: "RBASE-L Mailing List" <[email protected]> > > Subject: [RBASE-L] - Re: How to make this Delete command faster > > That's entirely possible. I did not notice that the column was varchar. >> Albert >> >> MDRD wrote: >> >>> Albert >>> >>> CREATE INDEX SxTC ON `TravCard` ( `Subjx` ASC ) >>> error >>> this works >>> CREATE INDEX SxTC ON `TravCard` ( `sympt1` ASC ) >>> >>> Subjx is a Varchar, Is Indexing Varchar is allowed?? >>> This is my first Varchar column. Marc >>> >>> >> >> > >
